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

runtime: "ThreadSanitizer: unexpected memory mapping" on ppc64le #54757

Closed
heschi opened this issue Aug 29, 2022 · 5 comments
Closed

runtime: "ThreadSanitizer: unexpected memory mapping" on ppc64le #54757

heschi opened this issue Aug 29, 2022 · 5 comments
Labels
compiler/runtime Issues related to the Go compiler and/or runtime. NeedsFix The path to resolution is known, but the work has not been done.
Milestone

Comments

@heschi
Copy link
Contributor

heschi commented Aug 29, 2022

2022-08-24T12:12:12-b5a9459/linux-ppc64le-buildlet
2022-08-20T00:18:04-28afa5b/linux-ppc64le-buildlet
2022-08-19T20:04:21-2cc6983/linux-ppc64le-power9osu
2022-08-19T17:46:07-4a530b8/linux-ppc64le-buildlet

##### ../misc/cgo/testsanitizers
--- FAIL: TestShared (0.00s)
    cshared_test.go:52: skipping msan_shared test on linux/ppc64le; -msan option is not supported.
    --- FAIL: TestShared/tsan_shared (2.64s)
        cshared_test.go:82: /workdir/tmp/TestShared848610845/tsan_shared exited with exit status 66
            FATAL: ThreadSanitizer: unexpected memory mapping 0x0d4223380000-0x0d4223480000
--- FAIL: TestTSAN (25.26s)
    --- FAIL: TestTSAN/tsan10 (1.28s)
        tsan_test.go:53: /workdir/tmp/TestTSAN1253881176/tsan10 exited with exit status 66
            FATAL: ThreadSanitizer: unexpected memory mapping 0x73db2eb00000-0x73db2ec00000
    --- FAIL: TestTSAN/tsan6 (1.28s)
        tsan_test.go:53: /workdir/tmp/TestTSAN2520017262/tsan6 exited with exit status 66
            FATAL: ThreadSanitizer: unexpected memory mapping 0x7e6058900000-0x7e6058a00000
    --- FAIL: TestTSAN/tsan7 (1.30s)
        tsan_test.go:53: /workdir/tmp/TestTSAN2125904041/tsan7 exited with exit status 66
            FATAL: ThreadSanitizer: unexpected memory mapping 0x7aa0e9a00000-0x7aa0e9b00000
    --- FAIL: TestTSAN/tsan11 (1.31s)
        tsan_test.go:53: /workdir/tmp/TestTSAN712299795/tsan11 exited with exit status 66
            FATAL: ThreadSanitizer: unexpected memory mapping 0x74b428600000-0x74b428700000
    --- FAIL: TestTSAN/tsan12 (1.36s)
        tsan_test.go:53: /workdir/tmp/TestTSAN75467294/tsan12 exited with exit status 66
            FATAL: ThreadSanitizer: unexpected memory mapping 0x71f29c600000-0x71f29c700000
    --- FAIL: TestTSAN/tsan4 (1.38s)
        tsan_test.go:53: /workdir/tmp/TestTSAN648519663/tsan4 exited with exit status 66
            FATAL: ThreadSanitizer: unexpected memory mapping 0x7c2a5f900000-0x7c2a5fa00000
    --- FAIL: TestTSAN/tsan5 (1.57s)
        tsan_test.go:53: /workdir/tmp/TestTSAN3675981625/tsan5 exited with exit status 66
            FATAL: ThreadSanitizer: unexpected memory mapping 0x7e6d31a00000-0x7e6d31b00000
    --- FAIL: TestTSAN/tsan2 (1.20s)
        tsan_test.go:53: /workdir/tmp/TestTSAN123276469/tsan2 exited with exit status 66
            FATAL: ThreadSanitizer: unexpected memory mapping 0x73d9edd00000-0x73d9ede00000
    --- FAIL: TestTSAN/tsan3 (1.26s)
        tsan_test.go:53: /workdir/tmp/TestTSAN2342781266/tsan3 exited with exit status 66
            FATAL: ThreadSanitizer: unexpected memory mapping 0x78bf9c900000-0x78bf9ca00000
    --- FAIL: TestTSAN/tsan9 (1.41s)
        tsan_test.go:53: /workdir/tmp/TestTSAN2129967694/tsan9 exited with exit status 66
            FATAL: ThreadSanitizer: unexpected memory mapping 0x7bb146000000-0x7bb146100000
FAIL

cc @golang/runtime @golang/ppc64

@heschi heschi added the NeedsFix The path to resolution is known, but the work has not been done. label Aug 29, 2022
@heschi heschi added this to the Go1.20 milestone Aug 29, 2022
@gopherbot gopherbot added the compiler/runtime Issues related to the Go compiler and/or runtime. label Aug 29, 2022
@ceseo
Copy link
Contributor

ceseo commented Aug 29, 2022

This looks like it's the same issue as #45040.

@heschi
Copy link
Contributor Author

heschi commented Aug 29, 2022

Thanks. In that case I think it'd make sense to change the test to either retry or skip the test when this error shows up.

@cherrymui
Copy link
Member

cherrymui commented Aug 29, 2022

I think CL https://go-review.git.corp.google.com/c/go/+/425355 addressed this? (By checking the C compiler version)

The failures are on Aug. 24 or earlier. The CL is submitted on Aug. 25.

@heschi
Copy link
Contributor Author

heschi commented Aug 29, 2022

Great, thank you.

@heschi heschi closed this as not planned Won't fix, can't repro, duplicate, stale Aug 29, 2022
@laboger
Copy link
Contributor

laboger commented Aug 29, 2022

Duplicate of #54645.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
compiler/runtime Issues related to the Go compiler and/or runtime. NeedsFix The path to resolution is known, but the work has not been done.
Projects
None yet
Development

No branches or pull requests

5 participants