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

github.com/googleapis/gax-go/v2/apierror: unrecognized failures #67292

Open
gopherbot opened this issue May 10, 2024 · 2 comments
Open

github.com/googleapis/gax-go/v2/apierror: unrecognized failures #67292

gopherbot opened this issue May 10, 2024 · 2 comments
Labels
NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.

Comments

@gopherbot
Copy link
Contributor

#!watchflakes
default <- pkg == "github.com/googleapis/gax-go/v2/apierror" && test == ""

Issue created automatically to collect these failures.

Example (log):

SIGSEGV: segmentation violation
PC=0x80cd278 m=1 sigcode=1 addr=0x81f22bb0

goroutine 0 gp=0x29806488 m=1 mp=0x29848008 [idle]:
runtime.fallback_nanotime()
	runtime/sys_freebsd_386.s:251 +0x18 fp=0x2982df58 sp=0x2982df34 pc=0x80cd278
runtime.nanotime1()
	runtime/vdso_freebsd.go:103 +0x40 fp=0x2982df6c sp=0x2982df58 pc=0x80c33a0
runtime.nanotime(...)
	runtime/time_nofake.go:19
...
edx    0x1
edi    0x8057f80
esi    0x1
ebp    0xffffffff
esp    0x2982df34
eip    0x80cd278
eflags 0x10202
cs     0x33
fs     0x13
gs     0x8f

watchflakes

@gopherbot gopherbot added the NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. label May 10, 2024
@gopherbot
Copy link
Contributor Author

Found new dashboard test flakes for:

#!watchflakes
default <- pkg == "github.com/googleapis/gax-go/v2/apierror" && test == ""
2024-05-10 14:42 freebsd-386-12_3 telemetry@f0a2a9af go@df4f40b9 github.com/googleapis/gax-go/v2/apierror [build] (log)
SIGSEGV: segmentation violation
PC=0x80cd278 m=1 sigcode=1 addr=0x81f22bb0

goroutine 0 gp=0x29806488 m=1 mp=0x29848008 [idle]:
runtime.fallback_nanotime()
	runtime/sys_freebsd_386.s:251 +0x18 fp=0x2982df58 sp=0x2982df34 pc=0x80cd278
runtime.nanotime1()
	runtime/vdso_freebsd.go:103 +0x40 fp=0x2982df6c sp=0x2982df58 pc=0x80c33a0
runtime.nanotime(...)
	runtime/time_nofake.go:19
...
edx    0x1
edi    0x8057f80
esi    0x1
ebp    0xffffffff
esp    0x2982df34
eip    0x80cd278
eflags 0x10202
cs     0x33
fs     0x13
gs     0x8f

watchflakes

@netixx
Copy link

netixx commented Jun 11, 2024

Not sure if it's related, but I had a similar sigsegv:

SIGSEGV: segmentation violation
PC=0x7ffc9a9cf930 m=1 sigcode=1

goroutine 0 [idle]:
runtime.nanotime(...)
      runtime/time_nofake.go:19
 runtime.sysmon()
      runtime/proc.go:5546 +0xb8 fp=0xc00014bfa0 sp=0xc00014bf38 pc=0x4495f8
runtime.mstart1()
     runtime/proc.go:1602 +0x93 fp=0xc00014bfc8 sp=0xc00014bfa0 pc=0x440f93
 runtime.mstart0()
      runtime/proc.go:1559 +0x76 fp=0xc00014bff8 sp=0xc00014bfc8 pc=0x440ed6
runtime.mstart()
      runtime/asm_amd64.s:394 +0x5 fp=0xc00014c000 sp=0xc00014bff8 pc=0x46ff85 

It's happening randomly after a few hours/days (I am not sure if the crash is always due to this sigsegv though).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Projects
Status: No status
Development

No branches or pull requests

2 participants