Merged
Conversation
4f94488 to
ced261f
Compare
ced261f to
5ce17ed
Compare
ianks
approved these changes
Apr 7, 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.

PRs #380 and #386 worked independently but broke grind tests when merged together. #380 added
configure_lazy_queue to the eager-mode path, setting entry_resolver on all queues including Grind. #386
reordered Static#poll to check entry_resolver before @index. Together, the grind queue's raw test ID strings
(e.g. "ATest#test_flaky") hit JSON.parse in LazyEntryResolver and crash, silently producing no results.
Additionally, even if the entries were JSON-formatted, the overhead of JSON.dump on millions of grind
entries consumed the entire --max-duration budget before any tests could run.
built by Static#populate
DELIMITER constant