chore: increase fuzz timeout to 5m

[JonathanOppenheimer]

Why this should be merged

We want to run fuzz tests in CI, and the current 2m is not enough time for fuzz to run without flaking. 5m seems like ample time, and would not bottleneck CI.

How this works

Changes 120s to 5m

How this was tested

CI

Need to be documented in RELEASES.md?

No

[Copilot]

Pull request overview

This PR increases the default go test timeout used by the repository’s test script to reduce CI flakiness when running fuzz tests.

Changes:

• Update the default go test timeout in scripts/build_test.sh from 120s to 5m (still overridable via TIMEOUT).

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[ARR4N]

It's really weird that this even takes 2 minutes. Locally it takes only 3 seconds to run the whole of go test ./vms/saevm/sae.

[JonathanOppenheimer]

It's really weird that this even takes 2 minutes. Locally it takes only 3 seconds to run the whole of go test ./vms/saevm/sae.

The average with the runners is about ~80s 🤷.

[alarso16]

What you linked isn't a fuzz test. It's a unit test with a subtest called "fuzz". This flake is known and well-understood, which would be addressed by #5292

[JonathanOppenheimer]

What you linked isn't a fuzz test. It's a unit test with a subtest called "fuzz". This flake is known and well-understood, which would be addressed by #5292

I was under the impression that increasing the time out for these fuzz subcases tests would fix the flake -- there's no --fuzz in the test build script, and we see the timeout in CI after 2 minutes which is what had currently been set. I will close this in favor of your PR which we should try to merge soon.