gvisor: Disable timerfd test

Somewhere between kernel 5.15 and 6.0 this syscall's behaviour has
changed.
The unit test expects -ESPIPE result but new kernels will return 0
(noop_llseek in the source).

The new solidrun board is our first CI machine to be running kernel 6.1
so this needs to be merged before that CI machine can be enabled.
This commit is contained in:
Ryan Houdek committed 2023-04-15 15:23:58 -07:00
1 parent 27c03f98d8
commit e8aaadb2d0
2 files changed
+10

No files matched your search

+5
View File
@@ -194,3 +194,8 @@ semaphore_test
# Since we are running these tests on a fully loaded system, we tend to context switch,
# causing the chance of a hang to occur quite frequently.
pselect_test
# Somewhere between kernel versions 5.15 and 6.0, timerfd lseek behaviour has changed.
# On older kernels it would return -ESPIPE, on new kernels it returns 0.
# This test expects -ESPIPE behaviour.
timerfd_test
+5
View File
@@ -220,3 +220,8 @@ semaphore_test
# Since we are running these tests on a fully loaded system, we tend to context switch,
# causing the chance of a hang to occur quite frequently.
pselect_test
# Somewhere between kernel versions 5.15 and 6.0, timerfd lseek behaviour has changed.
# On older kernels it would return -ESPIPE, on new kernels it returns 0.
# This test expects -ESPIPE behaviour.
timerfd_test