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

x/tools/internal/gcimporter: failures with signal: killed on linux-ppc64le-buildlet #56794

Closed
gopherbot opened this issue Nov 17, 2022 · 12 comments
Closed

x/tools/internal/gcimporter: failures with signal: killed on linux-ppc64le-buildlet #56794

gopherbot opened this issue Nov 17, 2022 · 12 comments
Labels
NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. Tools This label describes issues relating to any tools in the x/tools repository.
Milestone
Unreleased

Comments

@gopherbot
Copy link

gopherbot commented Nov 17, 2022 •
edited by bcmills 

#!watchflakes
post <- pkg == "golang.org/x/tools/internal/gcimporter" && test == "" && `signal: killed` && date < "2023-05-01"

Issue created automatically to collect these failures.

Example (log):

signal: killed

— watchflakes
@gopherbot gopherbot added NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. Tools This label describes issues relating to any tools in the x/tools repository. labels Nov 17, 2022
@gopherbot gopherbot added this to the Unreleased milestone Nov 17, 2022
@gopherbot
Copy link
Author

Found new dashboard test flakes for:

#!watchflakes
post <- pkg == "golang.org/x/tools/internal/gcimporter" && test == ""
2022-11-09 17:16 linux-ppc64le-buildlet tools@502c6347 go@2cea6cdb x/tools/internal/gcimporter (log) 
signal: killed

— watchflakes

@bcmills bcmills changed the title x/tools/internal/gcimporter: unrecognized failures x/tools/internal/gcimporter: failures with signal: killed on linux-ppc64le-buildlet Nov 17, 2022
@bcmills
Copy link
Contributor

bcmills commented Nov 17, 2022

May be the same root cause as #56793 (attn @golang/ppc64).

@bcmills
Copy link
Contributor

bcmills commented Nov 17, 2022

This could be related to the gcimporter changes in https://go.dev/cl/445455 (CC @matloob)

@pmur
Copy link
Contributor

pmur commented Nov 17, 2022

I suspect these failures around 9-10 Nov can be ignored. I was attempting to reproduce a gdb test timeout failure in a separate container which seems to have caused some spurious OOM kills on the P8/ppc64le VM.

@bcmills
Copy link
Contributor

bcmills commented Nov 17, 2022

Duplicate of #56794

@bcmills bcmills marked this as a duplicate of #56794 Nov 17, 2022
@bcmills bcmills closed this as not planned Won't fix, can't repro, duplicate, stale Nov 17, 2022
@bcmills
Copy link
Contributor

bcmills commented Nov 17, 2022

Oops, wrong issue. 😅

@bcmills bcmills reopened this Nov 17, 2022
@bcmills
Copy link
Contributor

bcmills commented Nov 17, 2022

Duplicate of #56793

@bcmills bcmills marked this as a duplicate of #56793 Nov 17, 2022
@bcmills bcmills closed this as not planned Won't fix, can't repro, duplicate, stale Nov 17, 2022
@gopherbot
Copy link
Author

Found new dashboard test flakes for:

#!watchflakes
post <- pkg == "golang.org/x/tools/internal/gcimporter" && test == ""
2023-05-25 16:41 linux-ppc64-sid-power10 tools@ed90c6d2 go@76bb0caa x/tools/internal/gcimporter (log) 
signal: killed

— watchflakes

@gopherbot gopherbot reopened this May 26, 2023
@pmur
Copy link
Contributor

pmur commented May 26, 2023

I think the recent failure on the power10 builders is the OOM/container related memory leak. I'll reboot both once the current jobs finish.

@gopherbot
Copy link
Author

Found new dashboard test flakes for:

#!watchflakes
post <- pkg == "golang.org/x/tools/internal/gcimporter" && test == ""
2023-11-09 21:01 linux-ppc64le-power10osu tools@e3f67986 go@130baf3d x/tools/internal/gcimporter (log) 
SIGQUIT: quit
PC=0x873fc m=0 sigcode=0

goroutine 2 [running]:
runtime.systemstack_switch()
	/workdir/go/src/runtime/asm_ppc64x.s:212 +0x10 fp=0xc00003cd70 sp=0xc00003cd50 pc=0x83180
runtime.(*mheap).freeSpan(...)
	/workdir/go/src/runtime/mheap.go:1551
runtime.(*sweepLocked).sweep(0x5a02c0?, 0x0)
	/workdir/go/src/runtime/mgcsweep.go:757 +0x73c fp=0xc00003ce78 sp=0xc00003cd70 pc=0x396fc
...
r20  0x54	r21  0x584680
r22  0x7ffff3f4ab70	r23  0xc00003cdf0
r24  0x561a40	r25  0x16
r26  0x0	r27  0x0
r28  0x0	r29  0xc000030258
r30  0x583a40	r31  0x1bee0
pc   0x873fc	ctr  0x0
link 0x48b50	xer  0x0
ccr  0x34448084	trap 0xc00
*** Test killed with quit: ran too long (22m0s).

— watchflakes

@gopherbot
Copy link
Author

Found new dashboard test flakes for:

#!watchflakes
post <- pkg == "golang.org/x/tools/internal/gcimporter" && test == ""
2023-11-10 13:59 linux-ppc64le-power10osu tools@92a8009c go@abf84221 x/tools/internal/gcimporter (log) 
SIGQUIT: quit
PC=0x875bc m=0 sigcode=0

goroutine 2 [running]:
	goroutine running on other thread; stack unavailable
created by runtime.init.5 in goroutine 1
	/workdir/go/src/runtime/proc.go:314 +0x2c

goroutine 3 [running]:
	goroutine running on other thread; stack unavailable
...
r20  0xaa	r21  0x5846e0
r22  0x7fffe31f23a0	r23  0xc000d42b10
r24  0xc000771930	r25  0xc000771908
r26  0xc003100c39	r27  0xc003100c35
r28  0x0	r29  0xc000032e98
r30  0x583aa0	r31  0x1c2b0
pc   0x875bc	ctr  0x0
link 0x48bd0	xer  0x0
ccr  0x34448024	trap 0xc00
*** Test killed with quit: ran too long (22m0s).

— watchflakes

@bcmills
Copy link
Contributor

bcmills commented Nov 10, 2023

The recent failures should be a new issue. Added a date restriction (#57632).

@bcmills bcmills closed this as not planned Won't fix, can't repro, duplicate, stale Nov 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. Tools This label describes issues relating to any tools in the x/tools repository.
Projects
Test Flakes
Status: Done
Milestone
Unreleased
Development

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