-
Notifications
You must be signed in to change notification settings - Fork 41.6k
Labels
kind/failing-testCategorizes issue or PR as related to a consistently or frequently failing test.Categorizes issue or PR as related to a consistently or frequently failing test.sig/api-machineryCategorizes an issue or PR as relevant to SIG API Machinery.Categorizes an issue or PR as relevant to SIG API Machinery.sig/nodeCategorizes an issue or PR as relevant to SIG Node.Categorizes an issue or PR as relevant to SIG Node.triage/acceptedIndicates an issue or PR is ready to be actively worked on.Indicates an issue or PR is ready to be actively worked on.
Description
Which jobs are failing?
https://prow.k8s.io/job-history/gs/kubernetes-jenkins/pr-logs/directory/pull-kubernetes-unit
Which tests are failing?
various
Since when has it been failing?
Oct 30 2023 6pm pst
Testgrid link
No response
Reason for failure (if possible)
Looks like different test are failing with connection timeout errors:
W1031 01:57:48.321545 61587 logging.go:59] [core] [Channel #244 SubChannel #246] grpc: addrConn.createTransport failed to connect to {Addr: "localhost:43189", ServerName: "localhost", }. Err: connection error: desc = "transport: Error while dialing: dial tcp 127.0.0.1:43189: connect: connection refused"
One of the tests triggered a core dump:
=== FAIL: pkg/kubelet/eviction TestManagerWithLocalStorageCapacityIsolationOpen (0.00s)
E1031 02:05:51.095814 44218 helpers.go:677] "Eviction manager: failed to construct signal" err="system container \"pods\" not found in metrics" signal="allocatableMemory.available"
I1031 02:05:51.095898 44218 helpers.go:750] "Eviction manager: no observation found for eviction signal" signal="allocatableMemory.available"
panic: runtime error: invalid memory address or nil pointer dereference [recovered]
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x18 pc=0x2bbae9b]
goroutine 140 [running]:
testing.tRunner.func1.2({0x2dfa500, 0x49e4720})
/usr/local/go/src/testing/testing.go:1545 +0x366
testing.tRunner.func1()
/usr/local/go/src/testing/testing.go:1548 +0x630
panic({0x2dfa500?, 0x49e4720?})
/usr/local/go/src/runtime/panic.go:920 +0x270
k8s.io/kubernetes/pkg/kubelet/eviction.(*managerImpl).evictPod(0xc0007754a0, {0x35a4a78, 0x4a53e80}, 0xc000964000, 0x0, {0xc000061040, 0x43}, 0x8?, 0x0)
/home/prow/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/pkg/kubelet/eviction/eviction_manager.go:591 +0xa7b
k8s.io/kubernetes/pkg/kubelet/eviction.(*managerImpl).emptyDirLimitEviction(0xc000964000?, {{{0x30ffd3d, 0x9}, {0x0, 0x0}, {0x30ffd3d, 0x9}}, {{0x0, 0x0, 0x0}}, ...}, ...)
/home/prow/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/pkg/kubelet/eviction/eviction_manager.go:514 +0x716
k8s.io/kubernetes/pkg/kubelet/eviction.(*managerImpl).localStorageEviction(0xc000775518?, {0xc0000840a0, 0x3, 0x0?}, 0xc0008f2400)
/home/prow/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/pkg/kubelet/eviction/eviction_manager.go:484 +0x1e8
k8s.io/kubernetes/pkg/kubelet/eviction.(*managerImpl).synchronize(0xc0007754a0, {0x3580c80, 0xc00039565f}, 0xc0007e1870)
/home/prow/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/pkg/kubelet/eviction/eviction_manager.go:336 +0x16f3
k8s.io/kubernetes/pkg/kubelet/eviction.TestManagerWithLocalStorageCapacityIsolationOpen(0xc000751520)
/home/prow/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/pkg/kubelet/eviction/eviction_manager_test.go:2028 +0x1051
testing.tRunner(0xc000751520, 0x3229210)
/usr/local/go/src/testing/testing.go:1595 +0x239
created by testing.(*T).Run in goroutine 1
/usr/local/go/src/testing/testing.go:1648 +0x82b
Anything else we need to know?
No response
Relevant SIG(s)
/sig
Metadata
Metadata
Assignees
Labels
kind/failing-testCategorizes issue or PR as related to a consistently or frequently failing test.Categorizes issue or PR as related to a consistently or frequently failing test.sig/api-machineryCategorizes an issue or PR as relevant to SIG API Machinery.Categorizes an issue or PR as relevant to SIG API Machinery.sig/nodeCategorizes an issue or PR as relevant to SIG Node.Categorizes an issue or PR as relevant to SIG Node.triage/acceptedIndicates an issue or PR is ready to be actively worked on.Indicates an issue or PR is ready to be actively worked on.