Skip to content

Commit 2f98d1e

Browse files
committed
Merge bitcoin/bitcoin#31814: ci: Bump fuzz task timeout
faca7ac ci: Bump fuzz task timeout (MarcoFalke) Pull request description: The fuzz task seems to be the most CPU intense task (going through GB of data through all fuzz inputs for all fuzz targets). Normally, the task takes 44 minutes (example https://cirrus-ci.com/task/5077976091459584), but under higher load, it may take longer (https://cirrus-ci.com/task/5966231095738368). I tried to move it to GHA to see how it compares, but it will be even slower there: https://github.com/maflcko/bitcoin-core-with-ci/actions/runs/13182526514/job/36796629409. The CI machines were recently updated to increase the CI performance, so in theory they could be updated again, but this can take some time and seems like the wrong fix anyway, because it will just hide the problem: Ideally fuzzing is fast and when evaluating a fuzz input takes more than 10 seconds, it feels more like a slow unit test loop. So ideally fuzz timeouts should be fixed (bitcoin/bitcoin#31066, bitcoin/bitcoin#30498, ...). However, this can also take time. So temporarily bump the fuzz timeout for now. ACKs for top commit: dergoegge: ACK faca7ac Tree-SHA512: cfb06d14712d94be6b28a17eee821dcc762453e8efbd9376200f8a0e784a55c2140e45ac48bee9b71ef6e85ae7345155dddc1239cbf0cd4bc02583848fe46308
2 parents f93d6cb + faca7ac commit 2f98d1e

File tree

1 file changed

+1
-0
lines changed

1 file changed

+1
-0
lines changed

.cirrus.yml

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -182,6 +182,7 @@ task:
182182
persistent_worker:
183183
labels:
184184
type: medium
185+
timeout_in: 240m # larger timeout, due to the high CPU demand
185186
env:
186187
FILE_ENV: "./ci/test/00_setup_env_native_fuzz.sh"
187188

0 commit comments

Comments
 (0)