diff options
| author | Michael Anthony Knyszek <mknyszek@google.com> | 2024-11-18 22:23:43 +0000 |
|---|---|---|
| committer | Michael Knyszek <mknyszek@google.com> | 2024-11-19 00:45:21 +0000 |
| commit | ec7824b6bb12481e7ffe50b7f1cbaa1faf465a44 (patch) | |
| tree | 64e220da2da3d77019e9f2062cd1a75f91c99e63 /src/internal/runtime/atomic | |
| parent | 79c0041daf1649a1b5374e7f59689558b67a969d (diff) | |
| download | go-ec7824b6bb12481e7ffe50b7f1cbaa1faf465a44.tar.xz | |
cmd/go: disable fuzz instrumentation for internal/godebug
This is thought to be the cause of certain recent longtest failures.
Let's try it out.
This appears to fix the longtests fuzz failures. I suspect that the
sync.Map in internal/godebug is at fault with the implementation
changing. I'm not sure yet exactly why this is a problem, maybe inlining
that didn't happen before? I don't know exactly when coverage
instrumentation happens in the compiler, but this is definitely the
problem.
For good measure, let's add internal/sync. If sync is on the list,
internal/sync should be, too.
Fixes #70429.
Fixes #70430.
Fixes #70431.
Change-Id: Ic9f49daa0956e3a50192bcc7778983682b5d12b8
Cq-Include-Trybots: luci.golang.try:gotip-linux-amd64-longtest
Reviewed-on: https://go-review.googlesource.com/c/go/+/629475
Reviewed-by: Roland Shoemaker <roland@golang.org>
LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
Diffstat (limited to 'src/internal/runtime/atomic')
0 files changed, 0 insertions, 0 deletions