Skip to content

test: further fix the timeout test to avoid false failures #693

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jul 15, 2025
Merged

test: further fix the timeout test to avoid false failures #693

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 6 additions & 5 deletions check/features.frm
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -303,12 +303,13 @@ assert succeeded?
#timeoutafter 0
.end
#require unix?
# ParFORM may terminate without printing the error message,
# depending on the MPI environment.
# Sometimes, FORM can terminate without printing the error message, so don't
# assert anything. We only test whether this hits the test suite timeout limit,
# or not. TODO in principle this can be considered to be a bug, to be looked at
# in the future.
# For parform, there is no attempt to ensure the master process recieves SIGALRM
# and not the workers.
#pend_if mpi?
# Sometimes, FORM will terminate after 1s without a runtime error.
# TODO: this should be considered a bug.
assert succeeded? || runtime_error?
*--#] TimeoutAfter_2 :
*--#[ dedup :
* Test deduplication
Expand Down
Loading