-
Notifications
You must be signed in to change notification settings - Fork 24.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
Transforms mixed cluster "GET/start/stop old [cluster/batch] transforms" tests fail reproducibly #67945
Comments
Pinging @elastic/ml-core (:ml/Transform) |
This bug only occurs on
@gwbrown: Do you think one of the above could take place here? |
1 or 3 are possible, though I did also check on latest I don't think it's 2, because just checking 3 PRs this has hit, there's one that adjusts some searchable snapshots test code (#67917), one that adjusts how timestamps are printed (#67893), and one that makes changes to snapshots (#63513), none of which should impact serialization of Transforms. If you believe this has been addressed and this repro line produces local failures for some reason which has already been addressed, feel free to close this issue and we can reopen it if/when it happens again. |
The last occurrence of this issue is from 2 days ago. I'll wait a day or two, look at build-stats and then close this issue if no new occurrences show up. |
I confirm that there were no new occurrences in the last days. |
Build scan: https://gradle-enterprise.elastic.co/s/apxwwc63asjom
Repro line:
./gradlew clean ':x-pack:qa:rolling-upgrade:v7.12.0#oneThirdUpgradedTest' -Dtests.class="org.elasticsearch.upgrades.UpgradeClusterClientYamlTestSuiteIT" -Dtests.method="test {p0=mixed_cluster/80_transform_jobs_crud/Test GET, start, and stop old cluster batch transforms}" -Dtests.seed=562A6BADAD918E4D -Dtests.security.manager=true -Dtests.bwc=true -Dtests.locale=es-MX -Dtests.timezone=W-SU -Druntime.java=11 -Dtests.rest.suite=mixed_cluster
Reproduces locally?: Yes
Applicable branches: Observed on
master
-based PR branches, typically (always?) during BWC tests against 7.x (7.12.0 at time of writing).Failure history: build-stats, these failures appear to have started on either Jan. 18 or Jan. 21, there are some similar-but-not-quite-the-same failures on the 18th, the exact error message first appears on the 21st.
There appear to be some similar failures for the
continuous transforms
version of this test as well, see this build scan. I haven't put much time into investigating that failure as my guess is that the root cause is the same.Failure excerpt:
The text was updated successfully, but these errors were encountered: