ewd998: raise EWD998_proof budget from 4 to 6 minutes - #221
Merged
Conversation
The 4-minute budget I set in tlaplus#218 is marginal on the macOS runners. It passes most of the time and was killed at the wall in run 31000876116, with the proof itself unaffected: 54195 Killed: 9 timeout --signal=KILL 4m ... EWD998_proof.tla Measured locally with tlapm 4600b24 and --stretch 5: 86 seconds, all 850 obligations proved. CONTRIBUTING suggests budgeting up to twice the local time, which is where 4 came from; the macOS runner needed more than 2.8x. Six minutes gives roughly 4x local headroom. Co-authored-by: Claude Opus 5 <noreply@anthropic.com> Signed-off-by: Vasilis Nasopoulos <vasilis_nasopoulos@hotmail.com>
vasilisnasopoulos
force-pushed
the
ewd998-proof-timeout
branch
from
August 5, 2026 14:55
01092ca to
9c688f8
Compare
Member
|
Enforcing strict time constraints using a wallclock is generally noisy and prone to false alarms. This is an infrastructure issue that can be addressed in the long term by implementing features like the recently added rlimit support. |
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
2 participants
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 4-minute budget I set in #218 is marginal on the macOS runners: it passes most of the time, and was killed at the wall in this run.
The proof itself is unaffected — the other five jobs in the same run proved it. Measured locally (tlapm 4600b24,
--stretch 5): 86 seconds, all 850 obligations proved.CONTRIBUTING.mdsuggests budgeting up to twice the local time on a fast machine, which is where 4 came from. The macOS runner needed more than 2.8x. Six minutes gives roughly 4x local headroom, which should stop this recurring.Noticed because it surfaced as an unrelated failure on #220.