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

Flaky test on k8sclusterreceiver #5973

Open
jpkrohling opened this issue Oct 28, 2021 · 5 comments
Open

Flaky test on k8sclusterreceiver #5973

jpkrohling opened this issue Oct 28, 2021 · 5 comments
Assignees
@asuresh4
Labels
bug Something isn't working ci-cd CI, CD, testing, build issues flaky test a test is flaky receiver/k8scluster

Comments

@jpkrohling
Copy link
Member

Seen on https://github.com/open-telemetry/opentelemetry-collector-contrib/runs/4031747516?check_suite_focus=true

make[2]: Entering directory '/home/runner/work/opentelemetry-collector-contrib/opentelemetry-collector-contrib/receiver/k8sclusterreceiver'
go test -race -timeout 300s --tags="" ./...
E1028 07:57:41.267867   42008 runtime.go:78] Observed a panic: "invalid memory address or nil pointer dereference" (runtime error: invalid memory address or nil pointer dereference)
goroutine 55 [running]:
k8s.io/apimachinery/pkg/util/runtime.logPanic({0x22ad360, 0x3694e00})
	/home/runner/go/pkg/mod/k8s.io/apimachinery@v0.22.2/pkg/util/runtime/runtime.go:74 +0xe6
k8s.io/apimachinery/pkg/util/runtime.HandleCrash({0x0, 0x0, 0xc000021738})
	/home/runner/go/pkg/mod/k8s.io/apimachinery@v0.22.2/pkg/util/runtime/runtime.go:48 +0xb0
panic({0x22ad360, 0x3694e00})
	/opt/hostedtoolcache/go/1.17.2/x64/src/runtime/panic.go:1047 +0x266
k8s.io/client-go/tools/cache.(*Reflector).ListAndWatch.func1(0xc000198380, 0xc00002c360, 0xc00021c120, 0xc000021988)
	/home/runner/go/pkg/mod/k8s.io/client-go@v0.22.2/tools/cache/reflector.go:319 +0xf54
k8s.io/client-go/tools/cache.(*Reflector).ListAndWatch(0xc000198380, 0xc00021c120)
	/home/runner/go/pkg/mod/k8s.io/client-go@v0.22.2/tools/cache/reflector.go:360 +0x316
k8s.io/client-go/tools/cache.(*Reflector).Run.func1()
	/home/runner/go/pkg/mod/k8s.io/client-go@v0.22.2/tools/cache/reflector.go:221 +0x45
k8s.io/apimachinery/pkg/util/wait.BackoffUntil.func1(0xc0001b9638)
	/home/runner/go/pkg/mod/k8s.io/apimachinery@v0.22.2/pkg/util/wait/wait.go:155 +0x82
k8s.io/apimachinery/pkg/util/wait.BackoffUntil(0xc0001b6140, {0x27dad40, 0xc00012e410}, 0x1, 0xc00021c120)
	/home/runner/go/pkg/mod/k8s.io/apimachinery@v0.22.2/pkg/util/wait/wait.go:156 +0xcf
k8s.io/client-go/tools/cache.(*Reflector).Run(0xc000198380, 0xc00021c120)
	/home/runner/go/pkg/mod/k8s.io/client-go@v0.22.2/tools/cache/reflector.go:220 +0x2df
k8s.io/apimachinery/pkg/util/wait.(*Group).StartWithChannel.func1()
	/home/runner/go/pkg/mod/k8s.io/apimachinery@v0.22.2/pkg/util/wait/wait.go:56 +0x3f
k8s.io/apimachinery/pkg/util/wait.(*Group).Start.func1()
	/home/runner/go/pkg/mod/k8s.io/apimachinery@v0.22.2/pkg/util/wait/wait.go:73 +0x7f
created by k8s.io/apimachinery/pkg/util/wait.(*Group).Start
	/home/runner/go/pkg/mod/k8s.io/apimachinery@v0.22.2/pkg/util/wait/wait.go:71 +0xdf
panic: runtime error: invalid memory address or nil pointer dereference [recovered]
	panic: runtime error: invalid memory address or nil pointer dereference

goroutine 55 [running]:
k8s.io/apimachinery/pkg/util/runtime.HandleCrash({0x0, 0x0, 0xc000021738})
	/home/runner/go/pkg/mod/k8s.io/apimachinery@v0.22.2/pkg/util/runtime/runtime.go:55 +0x145
panic({0x22ad360, 0x3694e00})
	/opt/hostedtoolcache/go/1.17.2/x64/src/runtime/panic.go:1047 +0x266
k8s.io/client-go/tools/cache.(*Reflector).ListAndWatch.func1(0xc000198380, 0xc00002c360, 0xc00021c120, 0xc000021988)
	/home/runner/go/pkg/mod/k8s.io/client-go@v0.22.2/tools/cache/reflector.go:319 +0xf54
k8s.io/client-go/tools/cache.(*Reflector).ListAndWatch(0xc000198380, 0xc00021c120)
	/home/runner/go/pkg/mod/k8s.io/client-go@v0.22.2/tools/cache/reflector.go:360 +0x316
k8s.io/client-go/tools/cache.(*Reflector).Run.func1()
	/home/runner/go/pkg/mod/k8s.io/client-go@v0.22.2/tools/cache/reflector.go:221 +0x45
k8s.io/apimachinery/pkg/util/wait.BackoffUntil.func1(0xc0001b9638)
	/home/runner/go/pkg/mod/k8s.io/apimachinery@v0.22.2/pkg/util/wait/wait.go:155 +0x82
k8s.io/apimachinery/pkg/util/wait.BackoffUntil(0xc0001b6140, {0x27dad40, 0xc00012e410}, 0x1, 0xc00021c120)
	/home/runner/go/pkg/mod/k8s.io/apimachinery@v0.22.2/pkg/util/wait/wait.go:156 +0xcf
k8s.io/client-go/tools/cache.(*Reflector).Run(0xc000198380, 0xc00021c120)
	/home/runner/go/pkg/mod/k8s.io/client-go@v0.22.2/tools/cache/reflector.go:220 +0x2df
k8s.io/apimachinery/pkg/util/wait.(*Group).StartWithChannel.func1()
	/home/runner/go/pkg/mod/k8s.io/apimachinery@v0.22.2/pkg/util/wait/wait.go:56 +0x3f
k8s.io/apimachinery/pkg/util/wait.(*Group).Start.func1()
	/home/runner/go/pkg/mod/k8s.io/apimachinery@v0.22.2/pkg/util/wait/wait.go:73 +0x7f
created by k8s.io/apimachinery/pkg/util/wait.(*Group).Start
	/home/runner/go/pkg/mod/k8s.io/apimachinery@v0.22.2/pkg/util/wait/wait.go:71 +0xdf
FAIL	github.com/open-telemetry/opentelemetry-collector-contrib/receiver/k8sclusterreceiver	0.131s
@jpkrohling jpkrohling added the bug Something isn't working label Oct 28, 2021
@jpkrohling jpkrohling mentioned this issue Oct 28, 2021
Merged
@skyduo
Copy link
Contributor

skyduo commented Oct 28, 2021 •
edited
Loading

same error in the health check pr #5643

@jpkrohling jpkrohling added the ci-cd CI, CD, testing, build issues label Oct 29, 2021
@mx-psi mx-psi added the flaky test a test is flaky label Nov 5, 2021
@github-actions
Copy link
Contributor

github-actions bot commented Nov 7, 2022

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

@github-actions github-actions bot added the Stale label Nov 7, 2022
@github-actions
Copy link
Contributor

Pinging code owners: @dmitryax. See Adding Labels via Comments if you do not have permissions to add labels yourself.

@github-actions
Copy link
Contributor

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

@github-actions github-actions bot added the Stale label Jan 30, 2023
@fatsheep9146 fatsheep9146 added never stale Issues marked with this label will be never staled and automatically removed and removed Stale labels Jan 30, 2023
@atoulme
Copy link
Contributor

atoulme commented Feb 14, 2024

Is this issue really worthy of being marked never stale? Can we close it as no reports have been made in over 2 years?

@TylerHelmuth TylerHelmuth removed the never stale Issues marked with this label will be never staled and automatically removed label Nov 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@asuresh4 asuresh4

Labels
bug Something isn't working ci-cd CI, CD, testing, build issues flaky test a test is flaky receiver/k8scluster
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
7 participants
@jpkrohling @atoulme @mx-psi @fatsheep9146 @TylerHelmuth @asuresh4 @skyduo