Skip to content
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.

Sign up for GitHub

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

Jump to bottom

test: Test timed out on Debian riscv64 builders #61437

Closed
yuzibo opened this issue Jul 19, 2023 · 5 comments
Closed

test: Test timed out on Debian riscv64 builders #61437

yuzibo opened this issue Jul 19, 2023 · 5 comments
Labels
arch-riscv Issues solely affecting the riscv64 architecture. WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided.

Comments

@yuzibo
Copy link

yuzibo commented Jul 19, 2023

What version of Go are you using (go version)?

$ go version
1.21

Does this issue reproduce with the latest release?

yes.

The gloang-1.21~rc3 always build failed due to:

##### ../test
panic: test timed out after 10m0s
running tests:
	Test (10m0s)
	Test/rotate0.go (14s)
	Test/rotate1.go (17s)
	Test/rotate2.go (18s)
	Test/rotate3.go (20s)

goroutine 6968 [running]:
panic({0x16fda0?, 0x3f38a5a3c0?})
	/usr/lib/go-1.21/src/runtime/panic.go:1017 +0x3a0 fp=0x3f3863cf10 sp=0x3f3863ce60 pc=0x470f8
testing.(*M).startAlarm.func1()
	/usr/lib/go-1.21/src/testing/testing.go:2259 +0x304 fp=0x3f3863cfd8 sp=0x3f3863cf10 pc=0xed68c
runtime.goexit()
	/usr/lib/go-1.21/src/runtime/asm_riscv64.s:512 +0x4 fp=0x3f3863cfd8 sp=0x3f3863cfd8 pc=0x7b034
created by time.goFunc
	/usr/lib/go-1.21/src/time/sleep.go:176 +0x50
...

The buildd log is here0.
I have checked other issues on here I think this issue is different from the others.
So I open the issue. Please let me know if any issues.
@bcmills
Copy link
Contributor

bcmills commented Jul 19, 2023

@yuzibo, it doesn't look like any particular test ended up deadlocked. You may need to set GO_TEST_TIMEOUT_SCALE to higher multiplier when running run.bash.

@bcmills bcmills added the WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided. label Jul 19, 2023
@bcmills
Copy link
Contributor

bcmills commented Jul 19, 2023

FWIW, the linux/riscv64 builders used by the Go project set GO_TEST_TIMEOUT_SCALE=4:
https://cs.opensource.google/go/x/build/+/master:dashboard/builders.go;l=2990-3020;drc=4a55ba2180ead88edfe88e9b5a27f17562900da0

@bcmills bcmills added WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided. and removed WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided. labels Jul 19, 2023
@bcmills bcmills changed the title test timed out on riscv64 for golang-1.21 test: Test timed out on Debian riscv64 builders Jul 19, 2023
@bcmills bcmills added the arch-riscv Issues solely affecting the riscv64 architecture. label Jul 19, 2023
@yuzibo
Copy link
Author

yuzibo commented Jul 20, 2023

IIRC The Debian builder has set the value to GO_TEST_TIMEOUT_SCALE=10, I will increase it and test it again.

@bcmills
Copy link
Contributor

bcmills commented Jul 20, 2023

Ah! In that case this is probably a duplicate of #61468.

@bcmills
Copy link
Contributor

bcmills commented Jul 20, 2023

Duplicate of #61468

@bcmills bcmills marked this as a duplicate of #61468 Jul 20, 2023
@bcmills bcmills closed this as not planned Won't fix, can't repro, duplicate, stale Jul 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
arch-riscv Issues solely affecting the riscv64 architecture. WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@bcmills @yuzibo