Skip to content

[CI] Vagrant tests fail with logging error #27521

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
jpountz opened this issue Nov 24, 2017 · 3 comments
Closed

[CI] Vagrant tests fail with logging error #27521

jpountz opened this issue Nov 24, 2017 · 3 comments
Assignees
@jasontedor
Labels
blocker >test-failure Triaged test failures from CI v6.1.0

Comments

@jpountz
Copy link
Contributor

jpountz commented Nov 24, 2017

See eg. https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+master+packaging-tests/2175/console.

not ok 69 [TAR PLUGINS] install jvm-example with different logging modes and check output
not ok 69 [TAR PLUGINS] install jvm-example with different logging modes and check output

This started failing after core-cli was made its own module #27114, so it might be related? cc @hub-cap
@jpountz jpountz added the >test-failure Triaged test failures from CI label Nov 24, 2017
@jasontedor
Copy link
Member

I think there is a bad bug here and this is a blocker for 6.1.0.

@jpountz
Copy link
Contributor Author

jpountz commented Nov 24, 2017

OK, I added labels.

@jasontedor jasontedor self-assigned this Nov 24, 2017
@jasontedor jasontedor mentioned this issue Nov 24, 2017
Merged
@jasontedor
Copy link
Member

I opened #27523.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jasontedor jasontedor

Labels
blocker >test-failure Triaged test failures from CI v6.1.0
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jpountz @jasontedor