Repository navigation
Conversation
mirai's .timeout clock starts when a task is submitted. muttest() queued every mutant up front, so once total run time exceeded `timeout` all remaining mutants were recorded as 'Timed out' errors. Submit at most `workers` mutants at a time instead. Co-Authored-By: Claude <noreply@anthropic.com>
A mutant that crashed its mirai daemon (e.g. a segfault in compiled code) or timed out in code ignoring interrupts left no usable daemon, so every later mutant waited out the full timeout and the run appeared to hang. Restart the daemons after such a failure and resubmit in-flight mutants. Report crashes as 'Test process crashed' rather than 'Timed out'. Co-Authored-By: Claude <noreply@anthropic.com>
This branch has not been deployed
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.
Three bug fixes, each with a regression test and (where user-visible) a NEWS entry.
timeoutnow applies to each mutant, not from submission. mirai's.timeoutclock starts when a task is submitted, andmuttest()submitted every mutant up front. Once the total run time exceededtimeout, all remaining mutants were reported as "Timed out". Mutants are now submitted at mostworkersat a time.ProgressMutationReporterprinted the wrong diff when a mutation added or removed lines.