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

cmd/go: TestQEMUUserMode is flaky #35457

Closed
bcmills opened this issue Nov 8, 2019 · 3 comments
Closed

cmd/go: TestQEMUUserMode is flaky #35457

bcmills opened this issue Nov 8, 2019 · 3 comments
Labels
FrozenDueToAge NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. Testing An issue that has been verified to require only test changes, not just a test failure.
Milestone
Go1.14

Comments

@bcmills
Copy link
Contributor

bcmills commented Nov 8, 2019 

--- FAIL: TestQEMUUserMode (14.30s)
    go_test.go:5220: running testgo [build -o /workdir/tmp/cmd-go-test-222073569/gotest753566098/main /workdir/tmp/cmd-go-test-222073569/gotest753566098/main.go]
    --- FAIL: TestQEMUUserMode/arm (8.26s)
        go_test.go:5224: qemu-arm output:
            qemu: uncaught target signal 11 (Segmentation fault) - core dumped
            
        go_test.go:5225: qemu-arm failed with signal: segmentation fault (core dumped)
    go_test.go:5220: running testgo [build -o /workdir/tmp/cmd-go-test-222073569/gotest753566098/main /workdir/tmp/cmd-go-test-222073569/gotest753566098/main.go]
FAIL
FAIL	cmd/go	109.906s

QEMU user-mode is nominally working (#13024), but mostly untested apart from this one test (see #1508). This unit-test asserts that a simple “hello world” binary can be run, but doesn't verify that any more realistic program actually works, and it practice it appears that realistic programs do not, in fact, work in QEMU user mode (#35254).

2019-11-08T15:10:39-52aebe8/linux-amd64-sid
2019-11-08T00:07:43-33dfd35/linux-amd64-sid
2019-11-07T21:59:39-953cc74/linux-amd64-sid
2019-11-07T21:59:16-4cde749/linux-amd64-sid
2019-11-07T20:34:27-4751db9/linux-amd64-sid
2019-11-07T14:51:06-543c6d2/aix-ppc64
2019-11-07T08:25:32-7a2baa9/freebsd-386-11_2
2019-11-07T08:25:32-7a2baa9/solaris-amd64-oraclerel
2019-11-05T18:37:06-c3cef0b/solaris-amd64-oraclerel
2019-11-05T16:31:48-414c1d4/solaris-amd64-oraclerel
2019-11-05T14:34:56-79a00a3/darwin-amd64-10_11
2019-11-05T00:00:36-e341e93/darwin-amd64-10_11
@bcmills bcmills added Testing An issue that has been verified to require only test changes, not just a test failure. NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. labels Nov 8, 2019
@bcmills bcmills added this to the Go1.14 milestone Nov 8, 2019
@bradfitz
Copy link
Contributor

bradfitz commented Nov 8, 2019

t.Skip for Go 1.14 and Backlog this?

@bcmills
Copy link
Contributor Author

bcmills commented Nov 8, 2019

I was thinking just delete the test, actually. (IMO #1508 is the proper solution.)

This test-case sporadically detects regressions in a platform that we don't actually support or test. It flags failures, but (without a full builder) ~nobody is actually going to do anything about those failures.

@gopherbot
Copy link
Contributor

Change https://golang.org/cl/206137 mentions this issue: cmd/go: delete flaky TestQEMUUserMode

@bcmills bcmills mentioned this issue Feb 3, 2020
Open
@golang golang locked and limited conversation to collaborators Nov 7, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
FrozenDueToAge NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. Testing An issue that has been verified to require only test changes, not just a test failure.
Projects
None yet
Milestone
Go1.14
Development

No branches or pull requests
3 participants
@bradfitz @bcmills @gopherbot