Repository navigation
fix(smt): do not wait for provers whose interrupt was lost - #1150
Merged
Merged
Conversation
When a prover answers, the remaining ones are interrupted and waited for. why3server kills the process group of a prover, but that group is created by the forked child itself. An interrupt sent right after the run request (typically when the first prover already answered while the next task was being prepared) can be handled before the group exists: the kill is silently lost and `smt` waits until the loser reaches its own time limit. Re-send the interrupt until the prover is reported as finished, instead of blocking on the first one. Retries start after 10ms and back off exponentially up to 1s.
strub
force-pushed
the
fix/smt-interrupt-race
branch
from
October 6, 2026 09:56
12f95e6 to
5f40c06
Compare
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
1 participant
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.
When a prover answers, the remaining ones are interrupted and waited
for. why3server kills the process group of a prover, but that group
is created by the forked child itself. An interrupt sent right after
the run request (typically when the first prover already answered
while the next task was being prepared) can be handled before the
group exists: the kill is silently lost and
smtwaits until theloser reaches its own time limit.
Re-send the interrupt until the prover is reported as finished,
instead of blocking on the first one. Retries start after 10ms and
back off exponentially up to 1s.