-
Notifications
You must be signed in to change notification settings - Fork 25.3k
Mute testSnapshotRestore in bcUpgradeTest #129767
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
Mute testSnapshotRestore in bcUpgradeTest #129767
Conversation
Pinging @elastic/es-core-infra (Team:Core/Infra) |
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 @ldematte. LGTM
@@ -15,4 +15,11 @@ tasks.register("bcUpgradeTest", StandaloneRestIntegTestTask) { | |||
usesBwcDistribution(Version.fromString("0.0.0")) | |||
systemProperty("tests.old_cluster_version", "0.0.0") | |||
onlyIf("tests.bwc.main.version system property exists") { System.getProperty("tests.bwc.main.version") != null } | |||
filter { | |||
// Mute problematic tests | |||
excludeTestsMatching("org.elasticsearch.upgrades.FullClusterRestartIT.testSnapshotRestore") |
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.
those class specific filters should be defined on the specific task not within the plugin in general IMO. That makes it easier to detect those filters for other engineers directly in the according build script without the need to dig into the plugin logic.
@@ -15,4 +15,11 @@ tasks.register("bcUpgradeTest", StandaloneRestIntegTestTask) { | |||
usesBwcDistribution(Version.fromString("0.0.0")) | |||
systemProperty("tests.old_cluster_version", "0.0.0") | |||
onlyIf("tests.bwc.main.version system property exists") { System.getProperty("tests.bwc.main.version") != null } | |||
filter { | |||
// Mute problematic tests |
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.
Can we add two words why those are problematic?
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.
The tests use string compare of version (from the cluster, saved in the snapshot) with tests.bwc.main.version
, which is far from ideal.
But I've investigated this a bit more, and I think we can fix this another way. See #129769
(ignore the IndexVersion change, it's there to test the change is working and will be reverted).
Still, in any case, this test assertion is.. not ideal. I'll contact distributed and see if they can do better.
@breskeby wdyt? Better to go with #129769, or mute these tests?
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'm fine with muting. but as said we should do it in the build script rather than here in the plugin
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.
Move filters to the specific projects; is that what you were thinking? (have I done it right?)
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.
yes thats what i meant :). Thank you.
💚 Backport successful
|
No description provided.