-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[Uptime] Unskip certs func tests #73086
[Uptime] Unskip certs func tests #73086
Conversation
Flaky test run passed, but an unrelated test had one failure: https://kibana-ci.elastic.co/job/kibana+flaky-test-suite-runner/654/. |
f063f67
to
7daa422
Compare
Second round of flaky test runner passed: https://kibana-ci.elastic.co/job/kibana+flaky-test-suite-runner/658/ |
Pinging @elastic/uptime (Team:uptime) |
@elasticmachine merge upstream |
Third run of flaky test runner passed x50, there were failures but none of the them were related to these tests: https://kibana-ci.elastic.co/job/kibana+flaky-test-suite-runner/661/. |
@elasticmachine merge upstream |
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.
@justinkambic i don't see any change beside un-skipping the test?
@shahzad31 this one was flaky because we sometimes ended up with two items when we were only expecting one. Could it be possible that we have updated the behavior of the list on the cert page at some point in the last month? I am having a really hard time reproducing this issue. |
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 just had a failure occur in 7.x https://kibana-ci.elastic.co/job/elastic+kibana+7.x/6833/
I don't think the fact that this is hard to reproduce means we should just re-enable the test as it's causing a real problem for other devs when it fails in PRs.
Yeah I wasn't aware of the recent failure when I made that comment. I'm going to need to delve deeper into this one. |
…s that can lead to test flakiness.
3d83dd7
to
b5b9ee9
Compare
Flaky test run with additional patch that should fix this issue: https://kibana-ci.elastic.co/job/kibana+flaky-test-suite-runner/680/ |
@spalger I ran this flaky test build and it seems to have only run the SSL tests in x-pack ci-group 6, and I can't figure out why I'm not seeing the certs test run. It's in that group. Parameters for the job are here: https://kibana-ci.elastic.co/job/kibana+flaky-test-suite-runner/680/parameters/ |
@elasticmachine merge upstream |
That doesn't seem to be the case to me, but it does look like the job timed out which is going to cause erratic failure reporting. You should probably lower the iteration count so that it can complete within the time limit. |
@elasticmachine merge upstream |
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, seems ok now, flkay runner are passing as well https://kibana-ci.elastic.co/job/kibana+flaky-test-suite-runner/709/
@spalger I think we're at a point now where it's worth a try unskipping. @shahzad31 added an improvement and I've updated the code that generates the data used by the test. The failures before were happening because we were expecting one item but received two; the field the objects are grouped by was different between two objects. I think now that field should be the same for any generated 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.
Sounds good, thanks for working on this and I hope it works!
@elasticmachine merge upstream |
💚 Build SucceededBuild metrics
History
To update your PR or re-run it, just comment with: |
* Temporarily unload all other functional tests. * Unskip certificates test. * Uncomment skipped test files. * Add explicit fields to check generator call to prevent grouping issues that can lead to test flakiness. * added wait for loading * update missing func Co-authored-by: Elastic Machine <[email protected]> Co-authored-by: Shahzad <[email protected]>
* Temporarily unload all other functional tests. * Unskip certificates test. * Uncomment skipped test files. * Add explicit fields to check generator call to prevent grouping issues that can lead to test flakiness. * added wait for loading * update missing func Co-authored-by: Elastic Machine <[email protected]> Co-authored-by: Shahzad <[email protected]>
Looks like this PR has backport PRs but they still haven't been merged. Please merge them ASAP to keep the branches relatively in sync. |
2 similar comments
Looks like this PR has backport PRs but they still haven't been merged. Please merge them ASAP to keep the branches relatively in sync. |
Looks like this PR has backport PRs but they still haven't been merged. Please merge them ASAP to keep the branches relatively in sync. |
* Temporarily unload all other functional tests. * Unskip certificates test. * Uncomment skipped test files. * Add explicit fields to check generator call to prevent grouping issues that can lead to test flakiness. * added wait for loading * update missing func Co-authored-by: Elastic Machine <[email protected]> Co-authored-by: Shahzad <[email protected]> Co-authored-by: Elastic Machine <[email protected]> Co-authored-by: Shahzad <[email protected]>
* Temporarily unload all other functional tests. * Unskip certificates test. * Uncomment skipped test files. * Add explicit fields to check generator call to prevent grouping issues that can lead to test flakiness. * added wait for loading * update missing func Co-authored-by: Elastic Machine <[email protected]> Co-authored-by: Shahzad <[email protected]> Co-authored-by: Elastic Machine <[email protected]> Co-authored-by: Shahzad <[email protected]>
Backported to: |
Summary
Fixes #70493.
We've had these tests skipped for some time. This patch attempts to update the tests to prevent flaky failures.
Checklist
Delete any items that are not applicable to this PR.
For maintainers