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
Currently, the fuzz tests sometimes take longer than 3 hours, despite my having recently reduced their iteration counts by half. This frequently causes PRs in the merge queue to time out waiting for CI results (for which the longest timeout we can set is 6 hours). Some optimizations are clearly needed.
The text was updated successfully, but these errors were encountered:
Update: I've eliminated some redundant CI runs with 505cf01, dae3b66 and 9348063, but we still need to improve CI-run performance since it can still be a bottleneck.
Currently, the fuzz tests sometimes take longer than 3 hours, despite my having recently reduced their iteration counts by half. This frequently causes PRs in the merge queue to time out waiting for CI results (for which the longest timeout we can set is 6 hours). Some optimizations are clearly needed.
The text was updated successfully, but these errors were encountered: