-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
[Infra] Attempt to fix flaky test #192091
[Infra] Attempt to fix flaky test #192091
Conversation
🤖 GitHub commentsExpand to view the GitHub comments
Just comment with:
|
Flaky Test Runner Stats🟠 Some tests failed. - kibana-flaky-test-suite-runner#6854[❌] x-pack/test/functional/apps/infra/config.ts: 9/50 tests passed. |
bfead39
to
9160263
Compare
Flaky Test Runner Stats🟠 Some tests failed. - kibana-flaky-test-suite-runner#6863[❌] x-pack/test/functional/apps/infra/config.ts: 0/50 tests passed. |
/ci |
'metricbeat-*', | ||
'logs-*', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note
These were not assigned to any metric type
loadTestFile(require.resolve('./metrics_anomalies')); | ||
loadTestFile(require.resolve('./metrics_explorer')); | ||
loadTestFile(require.resolve('./node_details')); | ||
loadTestFile(require.resolve('./hosts_view')); | ||
loadTestFile(require.resolve('./metrics_source_configuration')); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note
This test is potentially dangerous because it changes the index pattern, which could affect al subsequent tests if it fails to return the data to the original state.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In this case, could you add a comment to the code alerting about that and stating that it is best to keep it last?
Flaky Test Runner Stats🟠 Some tests failed. - kibana-flaky-test-suite-runner#6869[❌] x-pack/test/functional/apps/infra/config.ts: 0/25 tests passed. |
after(async () => kibanaServer.savedObjects.cleanStandardList()); | ||
before(async () => | ||
Promise.all([ | ||
esArchiver.load('x-pack/test/functional/es_archives/infra/alerts'), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note
This test was 100% dependent on the previous test running the alert archive.
Flaky Test Runner Stats🟠 Some tests failed. - kibana-flaky-test-suite-runner#6872[❌] x-pack/test/functional/apps/infra/config.ts: 0/25 tests passed. |
Flaky Test Runner Stats🟠 Some tests failed. - kibana-flaky-test-suite-runner#6875[❌] x-pack/test/functional/apps/infra/config.ts: 0/25 tests passed. |
/ci |
Flaky Test Runner Stats🎉 All tests passed! - kibana-flaky-test-suite-runner#6876[✅] x-pack/test/functional/apps/infra/config.ts: 25/25 tests passed. |
Pinging @elastic/obs-ux-infra_services-team (Team:obs-ux-infra_services) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
synthtrace change LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
await navigateToNodeDetails('host-1', 'host', { | ||
name: 'host-1', | ||
}); | ||
|
||
await pageObjects.header.waitUntilLoadingHasFinished(); | ||
await pageObjects.timePicker.setAbsoluteRange( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What's the reason why we don't need to navigate to the date with data?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We're setting the date picker with the same information in the test cases.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for fixing the tests, LGTM 🌟
💛 Build succeeded, but was flaky
Failed CI StepsMetrics [docs]
History
To update your PR or re-run it, just comment with: |
💔 All backports failed
Manual backportTo create the backport manually run:
Questions ?Please refer to the Backport tool documentation |
fixes [elastic#191806](elastic#191806) ## Summary It was a weird problem that could only be reproduced by running the host_view test after the node_details test. The cause was that the synthtrace data was not fully cleaned in between tests
Friendly reminder: Looks like this PR hasn’t been backported yet. |
Friendly reminder: Looks like this PR hasn’t been backported yet. |
2 similar comments
Friendly reminder: Looks like this PR hasn’t been backported yet. |
Friendly reminder: Looks like this PR hasn’t been backported yet. |
Friendly reminder: Looks like this PR hasn’t been backported yet. |
1 similar comment
Friendly reminder: Looks like this PR hasn’t been backported yet. |
fixes #191806
Summary
It was a weird problem that could only be reproduced by running the host_view test after the node_details test. The cause was that the synthtrace data was not fully cleaned in between tests