Update Semaphore test matrix to v2.19.12 - #7
Merged
Conversation
Document current Semaphore defects
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.
Summary
feature-shell-outputdefect profileValidation
qualityGate: passedStable-release defect found during validation
Short successful tasks can lose arbitrary stdout/stderr fragments in the persisted output on
v2.19.12. Initial concurrent matrix runs reproduced the same loss in otherwise successful Ansible
tasks across multiple databases and feature profiles. Retrying the output endpoint and adding a
final playbook delay did not recover the missing fragments, so this is not treated as eventual
consistency or hidden by retries.
The strict reproducer remains available through the manual
feature-shell-outputprofile and theinclude_shell_output_investigationworkflow input. Stable profile classes run sequentially toavoid amplifying the server-side collector race;
ProjectConcurrencyApiTeststill launches realconcurrent Semaphore tasks. The workaround and removal criteria are documented in
test-environment/shell-output-loss-defect.md.Upstream fixes already present after v2.19.12: