Skip to content

Cherry-pick #10179 to 6.x: Revert "Skip x-pack libbeat tests again as flaky (#10068)"#10259

Merged
ph merged 1 commit intoelastic:6.xfrom
ph:backport_10179_6.x
Jan 26, 2019
Merged

Cherry-pick #10179 to 6.x: Revert "Skip x-pack libbeat tests again as flaky (#10068)"#10259
ph merged 1 commit intoelastic:6.xfrom
ph:backport_10179_6.x

Conversation

@ph
Copy link
Copy Markdown
Contributor

@ph ph commented Jan 22, 2019

Cherry-pick of PR #10179 to 6.x branch. Original message:

This reverts commit edeed09.

Looking at this with a fresh eyes, I am not sure its flakyness, we should get log from the docker containers on failures.

@ph ph changed the title Cherry-pick #10179 to 6.x: [WIP] Revert "Skip x-pack libbeat tests again as flaky (#10068)" Cherry-pick #10179 to 6.x: Revert "Skip x-pack libbeat tests again as flaky (#10068)" Jan 22, 2019
@ph ph added the :Testing label Jan 22, 2019
@ph ph requested a review from ruflin January 22, 2019 18:21
@ph ph added the libbeat label Jan 22, 2019
@ruflin
Copy link
Copy Markdown
Contributor

ruflin commented Jan 23, 2019

Same as other PR, update to docker-compose need or going back to 2.1.

@ph
Copy link
Copy Markdown
Contributor Author

ph commented Jan 23, 2019

This will need #10299

@ph
Copy link
Copy Markdown
Contributor Author

ph commented Jan 25, 2019

I pushed the File based fix into this PR.

* Enable back CM integration suite

This reverts commit edeed09.

And do the following:

- Move all docker-compose.yml file to the version 2.3 format to have
support for `start_period`
- The health check check the cluster health instead of checking that the
host respond.
- Use the `ELASTIC_PASSWORD` variable instead of invoking the CLI.
- DUMP the last health check information and the docker-compose logs
@ph
Copy link
Copy Markdown
Contributor Author

ph commented Jan 26, 2019

Windows failures is due to #10346

@ph
Copy link
Copy Markdown
Contributor Author

ph commented Jan 26, 2019

Merging this test Pr is green master is green

@ph ph merged commit 3034357 into elastic:6.x Jan 26, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants