Repository navigation
Keep activity entry-safety tests scoped to their original run - #917
Merged
Merged
Conversation
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.



The full MySQL source suite fails before its activity entry-safety assertions: the fixture looks up ready workflow tasks globally and collides with a run left by an earlier database-truncation fixture. The isolated cases pass, which hid the dependency on test order.
Scope task, execution, history and repair-count checks to the original run. Add a control with another valid ready run and verify that its task and history remain unchanged while the target run still refuses the incompatible activity and records its original failure. All existing entry-safety assertions, retry expectations and runtime source are retained.
Evidence:
Refs #898. The already merged timeline correction is also included in the pending 2.12.0 changelog section, with no version change. The functional correction is test-only: no runtime, API, schema, dependency, version, native/shared/frozen or release-policy change. Fresh normal checks and publication remain required.