Link: Limit timeout for revcomp-blc-begin-ref.timeout future by bradcray · Pull Request #19818 · chapel-lang/chapel · GitHub
Merge pull request #19818 from bradcray/limit-valgrind-timeout
Limit timeout for revcomp-blc-begin-ref.timeout future
[trivial, not reviewed, but concept reviewed by @ronawho]
This future test switches between getting a nil dereference error and
timing out in its valgrind runs for reasons that aren't clear (task
scheduling? base address layout?), and I expect it would be hard to
make the failure more predictable without simply fixing the bug. The
change in behavior isn't problematic except that the default valgrind
timeout is quite high to give time for real programs to execute.
Here, I'm limiting the timeout to 10 seconds to avoid wasting time
because the program should either pass or fail in that amount of time.
Modified Files: A test/studies/shootout/reverse-complement/bradc/revcomp-blc-begin-ref.timeout Compare: https://github.com/chapel-lang/chapel/compare/7b882e8e0c24...eea8c324e2b5