-
Notifications
You must be signed in to change notification settings - Fork 18k
runtime: tests have gotten slower #48770
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Maybe related #48496 |
Ouch. Yes, quite possibly! |
@josharian #48496 seems to have been resolved. Is this any better? |
It is marginally better, but still much slower than previous releases.
Also, tip now contains log spam:
|
Mailed CL 364555 for the log spam. |
Change https://golang.org/cl/366256 mentions this issue: |
This test spends most of its time sleeping and waiting on a subprocess to sleep. It seems like a prime candidate to run in parallel, although we may need to relax its hard-coded 2s timeout on the sleep(1) subprocess. For #48770 Change-Id: I4e839739fe82446615f9894c1904c87e5f3cf386 Reviewed-on: https://go-review.googlesource.com/c/go/+/366256 Trust: Bryan C. Mills <bcmills@google.com> Run-TryBot: Bryan C. Mills <bcmills@google.com> Reviewed-by: Emmanuel Odeke <emmanuel@orijtech.com> Reviewed-by: Ian Lance Taylor <iant@golang.org> TryBot-Result: Go Bot <gobot@golang.org>
How are we doing here @josharian? |
Looks fixed. |
I've noticed running all.bash recently that the runtime tests are really slow and CPU intensive.
On my M1, I tried doing
cd $GOROOT/runtime; go test -c; ./runtime.test -test.short
with recent Go versions. The runtime tests now take almost 3x longer than 1.17.6.46 real 7.76 user 2.52 sys
7.39 real 8.40 user 2.48 sys
20.03 real 25.64 user 6.26 sys
The slowest at tip are:
Perhaps some of these could be shortened, skipped, or marked parallel?
The text was updated successfully, but these errors were encountered: