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
runtime: TestStackGrowth failures #57601
Comments
Found new dashboard test flakes for:
2022-11-29 01:18 openbsd-386-71 go@0fd7be7e runtime.TestStackGrowth (log)
2022-12-14 19:13 openbsd-386-71 go@5c682f94 runtime.TestStackGrowth (log)
|
This comment was marked as outdated.
This comment was marked as outdated.
https://build.golang.org/log/5571acfcf4d4d6de5d3f22b56f8c2dca2623f7cc ( |
Hmm, but that's also a test timeout, not specific to this test (which only ran, in parallel, for 14s). 🤔 |
Found new dashboard test flakes for:
2023-01-09 18:21 openbsd-386-71 go@8232a09e runtime.TestStackGrowth (log)
|
Found new dashboard test flakes for:
2023-04-19 14:12 linux-s390x-ibm go@8c2ff88c runtime.TestStackGrowth (log)
|
CC @golang/s390x |
@cherrymui Points out that there are a few other recent timeouts with TestStackGrowth in the stack trace on the dashboard. EDIT: All on the s390x builder. |
The failure is a timeout. The other two recent failures https://build.golang.org/log/2d9a742a943b0d7f50c911c513bf4c16b3ce058b and https://build.golang.org/log/a53fee808f7e6df733f45b19ee18a08d01a5fa5d are also timeout, and both have The test is expected to run 256 iterations. In the three failures they have run 167, 162, and 12 iterations, respectively. (The latter two seem the whole Is there any recent change on the S390X builder that could make things slower? |
I tried to run this test (in isolation) at tip on the s390x gomote, and the test runs pretty fast, taking about 1 second. Maybe some other tests running concurrently interfering with it? (from the log https://build.golang.org/log/1ffec993ba92cffdbf302b85265475af6f18639e it doesn't seem to have other tests running, though, at least at the time of the timeout.) Maybe we could try running the test not in parallel with other tests, to reduce interfering. For one, the test calls |
Change https://go.dev/cl/492715 mentions this issue: |
Found new dashboard test flakes for:
2023-05-03 18:47 linux-s390x-ibm go@ea9097c9 runtime.TestStackGrowth (log)
|
Found new dashboard test flakes for:
2023-06-24 05:24 linux-s390x-ibm go@a031f4ef runtime.TestStackGrowth (log)
|
Found new dashboard test flakes for:
2023-06-24 02:06 linux-s390x-ibm go@65092835 runtime.TestStackGrowth (log)
|
The new failures are all S390X and similar to #60413. |
Issue created automatically to collect these failures.
Example (log):
— watchflakes
The text was updated successfully, but these errors were encountered: