-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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.
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
Kibana stats integration test failling on version key not found. #11261
Comments
Pinging @elastic/stack-monitoring |
I've run this test locally about 20 times so far and no failures. I'd like to see from the next weekly flaky tests report if this is really a flaky test or a ephemeral failure. |
Since this is linked to a container, it's possible that the container is not completely ready in some cases. I've had similar issues with CM, worked successfully on a local (fast machine) but failed from time to time on Travis because of the slowness of the host. |
Good point, @ph. Any tips how you repro'd/resolved the issue in the CM cases? |
I was a bit more strict on the health check strategies in my docker compose file and added a grace period to start with @ycombinator What if you print the return of the API when there is an error? Maybe there is an error message when this happens? |
Thanks @ph, I'll start by printing out the API response upon error. Let's see what we're dealing with and then take it from there. |
To help debug elastic#11261. (cherry picked from commit 67ebca4)
I'm facing what seems to be this issue consistently at #11759
|
Sorry about that @odacremolbap. I'm skipping these tests for now while we debug them: #11807. |
found in https://travis-ci.org/elastic/beats/jobs/506466210
The text was updated successfully, but these errors were encountered: