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
Each fuzzer that is part of the nightly CI runs thousands of regression tests which, in one case, (unoptimized solc invocation) can take over 10 minutes to complete.
CircleCI times out such runs because it does not witness any output on the console.
Proposed solution: Print a "dot" every 5 minutes so as to not trigger a circle CI timeout.
The text was updated successfully, but these errors were encountered:
bshastry
changed the title
[ossfuzz
[ossfuzz] nightly CI times our because of no console output for over 10 minutes
Apr 29, 2019
bshastry
changed the title
[ossfuzz] nightly CI times our because of no console output for over 10 minutes
[ossfuzz] nightly CI times out because of no console output for over 10 minutes
Apr 29, 2019
Description
Each fuzzer that is part of the nightly CI runs thousands of regression tests which, in one case, (unoptimized solc invocation) can take over 10 minutes to complete.
CircleCI times out such runs because it does not witness any output on the console.
Proposed solution: Print a "dot" every 5 minutes so as to not trigger a circle CI timeout.
The text was updated successfully, but these errors were encountered: