Ranged Ingredient Test Failures#4884
Open
DilithiumThoride wants to merge 7 commits into
Open
Conversation
…ed Ingredient tests, to try to catch for spurious failures.
…ing failure logging. Increase multiblock run count to compensate. Extend output check delay slightly.
jurrejelle
approved these changes
Jun 1, 2026
Contributor
jurrejelle
left a comment
There was a problem hiding this comment.
hoping we get some clarity as to why, if this doesn't solve it 🫡
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.
What
Batched and Parallel Ranged Ingredient Tests sometimes fail for no apparent reason. Trying to replicate these failures locally has proved unreliable at best, with the failures being extremely inconsistent, and refusing to even log what they were.
We believe that the logging failures come from #4538 and the
attemptsparam; running tests with higherattemptscount does not print the assert log entries on failure.In an effort to find more information I've added an extra step of logging to the suspect tests based on This Failed Test Report as an exemplar.
Implementation Details
attemptsparam removed from ranged test cases, reverting Re-run ranged input tests multiple times #4538AI Usage
Agent Used
Claude, no further details as Jurre ran it on his end.
Agent Usage Description
Jurre fed the test code into Claude and asked it to figure out why it was generating so many silent failures. Claude and Jurre came back with the suspect conclusions of the
attemptsparam, and overly tight timings on test assertions. This was taken into advisement when making subsequent code changes, however No machine generated code was used in creating the PR.Outcome
Fewer spurious automated test failures, and/or more informative ones when they do fail?
How Was This Tested
Multiple hours of trying to make the tests fail locally (Gametests run, Gametests debug, deleting world between cycles, not deleting world between cycles) which failed to fail