-
Notifications
You must be signed in to change notification settings - Fork 25.2k
Make testDatafeedTimingStats_DatafeedJobIdUpdated test easier to debug #44206
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
Make testDatafeedTimingStats_DatafeedJobIdUpdated test easier to debug #44206
Conversation
Pinging @elastic/ml-core |
run elasticsearch-ci/packaging-sample |
run elasticsearch-ci/bwc |
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
"Closes #44196" is an optimistic statement, I'm not sure what the root cause it but the loop unrolling and unique names will help debugging and finding the failure in the log file. State is cleared between tests and jobs deleted so name clashes won't be problem (it is an error to create a job with the same name anyway).
...ve-multi-node-tests/src/test/java/org/elasticsearch/xpack/ml/integration/DatafeedJobsIT.java
Outdated
Show resolved
Hide resolved
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.
I've removed the "Closes #issue" form the description.
...ve-multi-node-tests/src/test/java/org/elasticsearch/xpack/ml/integration/DatafeedJobsIT.java
Outdated
Show resolved
Hide resolved
run elasticsearch-ci/bwc |
…d tests so that they do not clash with names from other tests * Unroll the loops so that it is easier to track down which iteration failed should the exception occur
8a9e4a9
to
d59543c
Compare
Related to: #44196