Fix stress tests always reporting success#95081
Merged
alexey-milovidov merged 1 commit intomasterfrom Jan 25, 2026
Merged
Conversation
The variable `test_results` was being overwritten with an empty list before the loop that was supposed to iterate over it, causing the loop to never execute and all stress tests to always report success. This bug was introduced in 97fe0b8 on December 16, 2025. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Contributor
|
Workflow [PR], commit [0780599] Summary: ❌
|
Member
Author
|
Amazing! Now it runs. |
Member
|
Thanks for the fix @alexey-milovidov! |
This was referenced Feb 6, 2026
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 variable
test_resultswas being overwritten with an empty list before the loop that was supposed to iterate over it, causing the loop to never execute and all stress tests to always report success.This bug was introduced in 97fe0b8 on December 16, 2025.
Changelog category (leave one):