diff options
author | Richard Purdie <richard.purdie@linuxfoundation.org> | 2022-02-14 16:20:18 +0000 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2022-02-16 09:46:24 +0000 |
commit | e8f5bd9dc35e2da014412bb35fbd2f96d0b1c5a8 (patch) | |
tree | 486dc6666a6aa4d423188ebf65618815fb78df7f /meta/recipes-extended/ltp/ltp | |
parent | 848a506a71d789a4c81df8bf04deaba42f5b5f51 (diff) | |
download | openembedded-core-contrib-e8f5bd9dc35e2da014412bb35fbd2f96d0b1c5a8.tar.gz |
ltp: Disable proc01 test
This test has history of hanging on arm trying to read from /proc/kmsg and it has
reappeared. Disable the test since hanging autobuilder builds are annoying. I suspect
there is a genuine race on ARM somewhere here in the kernel.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/recipes-extended/ltp/ltp')
-rw-r--r-- | meta/recipes-extended/ltp/ltp/disable_hanging_tests.patch | 27 |
1 files changed, 27 insertions, 0 deletions
diff --git a/meta/recipes-extended/ltp/ltp/disable_hanging_tests.patch b/meta/recipes-extended/ltp/ltp/disable_hanging_tests.patch new file mode 100644 index 0000000000..f25a692dc0 --- /dev/null +++ b/meta/recipes-extended/ltp/ltp/disable_hanging_tests.patch @@ -0,0 +1,27 @@ +This patch disables tests which we've found "hang" on our infrastructure. + +proc01: +https://autobuilder.yoctoproject.org/typhoon/#/builders/96/builds/1748 (arm) +https://autobuilder.yoctoproject.org/typhoon/#/builders/96/builds/1781 (arm) +https://autobuilder.yoctoproject.org/typhoon/#/builders/96/builds/2782 (arm) +(was trying to read /proc/kmsg, looks like a horrible test anyway) + +Upstream-Status: Inappropriate [OE Configuration] +Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> + +Index: git/runtest/fs +=================================================================== +--- git.orig/runtest/fs ++++ git/runtest/fs +@@ -64,11 +64,6 @@ writetest01 writetest + #Also run the fs_di (Data Integrity tests) + fs_di fs_di -d $TMPDIR + +-# Read every file in /proc. Not likely to crash, but does enough +-# to disturb the kernel. A good kernel latency killer too. +-# Was not sure why it should reside in runtest/crashme and won't get tested ever +-proc01 proc01 -m 128 +- + read_all_dev read_all -d /dev -p -q -r 3 + read_all_proc read_all -d /proc -q -r 3 + read_all_sys read_all -d /sys -q -r 3 |