From ad877d4088f4fa9e8d2dadbe8d993338c44dbbfc Mon Sep 17 00:00:00 2001 From: Ryan Houdek Date: Tue, 30 Mar 2021 15:29:52 -0700 Subject: [PATCH] Disables gvisor test proc_pid_oomscore_test Depending on runner this passes or fails. The test expects to be able to open `/proc/self/oom_score_adj` as writable to adjust the oom score. This is expected to fail on all three of our runners, but sometimes the solidrun board manages to open it. Disable as it is a flake. Could be a kernel bug on the solid run board --- unittests/gvisor-tests/Disabled_Tests | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/unittests/gvisor-tests/Disabled_Tests b/unittests/gvisor-tests/Disabled_Tests index 14271974e..3d00c96b6 100644 --- a/unittests/gvisor-tests/Disabled_Tests +++ b/unittests/gvisor-tests/Disabled_Tests @@ -67,4 +67,7 @@ timers_test # these are flaky on x86 itimer_test -stat_times_test \ No newline at end of file +stat_times_test + +# This periodically fails on ARM hosts. `PosixError(errno=13 Permission denied) open(/proc/self/oom_score_adj, 0x1, 0)` +proc_pid_oomscore_test