You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Likely more found in day to day PRs being run and failing due to this false test failure.
If this time limit is enforced by a requirement, then worth discussing if maybe test machine is set to use a 'fast' runner instead of a regular 'normal'. The trade off is a CPU with a higher clock speed, and the same amount of RAM.
The text was updated successfully, but these errors were encountered:
F-WRunTime
changed the title
Increasing the Kontrol set time for the "integration tests (booster)" to alleviate repeated failures due to hitting execution time limit.
Increasing the Kontrol test time limit on "integration tests (booster)"
Aug 8, 2024
To Alleviate the false failure of tests due to time limit restrictions, it's suggested to increase the time limit of these tests.
One Example of this
https://github.com/runtimeverification/kontrol/actions/runs/10283080073/job/28526574497?pr=750
Likely more found in day to day PRs being run and failing due to this false test failure.
If this time limit is enforced by a requirement, then worth discussing if maybe test machine is set to use a 'fast' runner instead of a regular 'normal'. The trade off is a CPU with a higher clock speed, and the same amount of RAM.
The text was updated successfully, but these errors were encountered: