From 905f07f1ac13f6a894bde3fef9adfdcbefa71da0 Mon Sep 17 00:00:00 2001 From: Todd Neal Date: Sun, 20 Aug 2023 13:38:07 -0500 Subject: [PATCH] Revert "mark the OOM killer as serial to reduce flakes" This reverts commit bd6f5487463e7232491403e474ee556d7cfe12a8. Running as serial didn't completely eliminate the flake so I think there's something more going on here. Reverting the change to serial since its not a solution. --- test/e2e_node/oomkiller_linux_test.go | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/test/e2e_node/oomkiller_linux_test.go b/test/e2e_node/oomkiller_linux_test.go index d78fcf5d680..d6353e45642 100644 --- a/test/e2e_node/oomkiller_linux_test.go +++ b/test/e2e_node/oomkiller_linux_test.go @@ -37,10 +37,7 @@ type testCase struct { oomTargetContainerName string } -// Marked as [Serial] since currently the runtime can miss the OOM event if the pod is killed too quickly. This seems -// to occur more often when the node is highly loaded. - -var _ = SIGDescribe("OOMKiller [LinuxOnly] [NodeConformance] [Serial]", func() { +var _ = SIGDescribe("OOMKiller [LinuxOnly] [NodeConformance]", func() { f := framework.NewDefaultFramework("oomkiller-test") f.NamespacePodSecurityLevel = admissionapi.LevelPrivileged