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.

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

runtime: "interface {} is nil, not *main.T" on linux-amd64-noopt builder #37401

Open
bcmills opened this issue Feb 24, 2020 · 2 comments
Open

runtime: "interface {} is nil, not *main.T" on linux-amd64-noopt builder #37401

bcmills opened this issue Feb 24, 2020 · 2 comments
Labels
compiler/runtime Issues related to the Go compiler and/or runtime. NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Milestone
Unplanned

Comments

@bcmills
Copy link
Contributor

bcmills commented Feb 24, 2020

2020-02-22T04:31:41-059a5ac/linux-amd64-noopt

# go run run.go -- fixedbugs/issue13169.go
exit status 1
panic: interface conversion: interface {} is nil, not *main.T

goroutine 34 [running]:
main.main.func2(0xc00008c060, 0xc00008c0c0)
	/workdir/go/test/fixedbugs/issue13169.go:40 +0xc0
created by main.main
	/workdir/go/test/fixedbugs/issue13169.go:38 +0xd4
exit status 2

FAIL	fixedbugs/issue13169.go	1.089s

See previously #13169 (CC @aclements, @randall77, @mknyszek).

Perhaps some operation that the runtime assumes to be atomic no longer is in noopt mode? (#36110 may be related; CC @cherrymui)
@bcmills bcmills added the NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. label Feb 24, 2020
@bcmills bcmills added this to the Go1.15 milestone Feb 24, 2020
@cherrymui
Copy link
Member

Perhaps some operation that the runtime assumes to be atomic no longer is in noopt mode?

I didn't mean that some atomic operations are not atomic in noopt mode. I meant it may be not intrinsified, which affects where the safe points are. That is specific to #36110.

@ianlancetaylor
Copy link
Contributor

These seems to have happened exactly once. Moving milestone to unplanned in case it ever happens again.

@ianlancetaylor ianlancetaylor modified the milestones: Go1.15, Unplanned Jun 16, 2020
@gopherbot gopherbot added the compiler/runtime Issues related to the Go compiler and/or runtime. label Jul 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
compiler/runtime Issues related to the Go compiler and/or runtime. NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Projects
None yet
Milestone
Unplanned
Development

No branches or pull requests
4 participants
@ianlancetaylor @bcmills @gopherbot @cherrymui