hi all, anyone familiar enough with running lkp-tests to recognize these errors ? 1st, from inside a virtme VM - bash-5.2# /usr/local/bin/lkp split-job --compatible /home/jimc/projects/lkp-tests.git/jobs/kmemleak-test.yaml /home/jimc/projects/lkp-tests.git/jobs/kmemleak-test.yaml => ./kmemleak-test-defaults.yaml bash-5.2# /usr/local/bin/lkp run ./kmemleak-test-defaults.yaml 2023-05-19 13:04:31 -0600 WARN -- Jobfile is a dirty file, better to run 'lkp split-job --compatible ./kmemleak-test-defaults.yaml' first sh: -c: line 1: syntax error near unexpected token `(' sh: -c: line 1: `grep -w '^memory:' /home/jimc/projects/lkp-tests.git/hosts/(none)' /home/jimc/projects/lkp-tests.git/bin/run-local:121:in `<main>': undefined method `chomp' for nil:NilClass (NoMethodError) job['memory'] ||= `grep -w '^memory:' #{LKP_SRC}/hosts/#{HOSTNAME}`.split(' ')[1].chomp ^^^^^^ bash-5.2# /usr/local/bin/lkp split-job --compatible ./kmemleak-test-defaults.yaml /tmp/20230519-534-276vfc => ./20230519-534-276vfc-defaults.yaml bash-5.2# /usr/local/bin/lkp run ./20230519-534-276vfc-defaults.yaml 2023-05-19 13:05:41 -0600 WARN -- Jobfile is a dirty file, better to run 'lkp split-job --compatible ./20230519-534-276vfc-defaults.yaml' first sh: -c: line 1: syntax error near unexpected token `(' sh: -c: line 1: `grep -w '^memory:' /home/jimc/projects/lkp-tests.git/hosts/(none)' /home/jimc/projects/lkp-tests.git/bin/run-local:121:in `<main>': undefined method `chomp' for nil:NilClass (NoMethodError) job['memory'] ||= `grep -w '^memory:' #{LKP_SRC}/hosts/#{HOSTNAME}`.split(' ')[1].chomp ^^^^^^ somehow, ruby is broken / unavailable inside the VM. 2 - on the host itself [jimc@frodo lkp-tests.git]$ sudo lkp run ./20230519-819840-khtr75-defaults.yaml [sudo] password for jimc: 2023-05-19 13:08:54 -0600 WARN -- Jobfile is a dirty file, better to run 'lkp split-job --compatible ./20230519-819840-khtr75-defaults.yaml' first current kernel cannot support kmemleak, please check CONFIG_DEBUG_KMEMLEAK /home/jimc/projects/lkp-tests.git/lib/debug.sh:12: die /home/jimc/projects/lkp-tests.git/tests/kmemleak-test:8: main :0: kill 825577 vmstat --timestamp -n 10 kill 825575 dmesg --follow --decode wait for background processes: 825579 meminfo grep: warning: stray \ before : grep: warning: stray \ before : 2023-05-19 13:08:58 WARN -- job exited due to die /lkp/result/kmemleak-test/defaults/frodo/fedora/defconfig/gcc/6.2.15-300.fc38.x86_64/3 grep: warning: stray \ before : 2023-05-19 13:08:58 WARN -- job exited due to die /lkp/result/kmemleak-test/defaults/frodo/fedora/defconfig/gcc/6.2.15-300.fc38.x86_64/3 grep: warning: stray \ before : 2023-05-19 13:08:58 WARN -- job exited due to die /lkp/result/kmemleak-test/defaults/frodo/fedora/defconfig/gcc/6.2.15-300.fc38.x86_64/3 grep: warning: stray \ before : 2023-05-19 13:08:58 WARN -- job exited due to die /lkp/result/kmemleak-test/defaults/frodo/fedora/defconfig/gcc/6.2.15-300.fc38.x86_64/3 grep: warning: stray \ before : 2023-05-19 13:08:58 WARN -- job exited due to die /lkp/result/kmemleak-test/defaults/frodo/fedora/defconfig/gcc/6.2.15-300.fc38.x86_64/3 grep: warning: stray \ before : 2023-05-19 13:08:58 WARN -- job exited due to die /lkp/result/kmemleak-test/defaults/frodo/fedora/defconfig/gcc/6.2.15-300.fc38.x86_64/3 grep: warning: stray \ before : grep: warning: stray \ before : 2023-05-19 13:08:58 WARN -- job exited due to die /lkp/result/kmemleak-test/defaults/frodo/fedora/defconfig/gcc/6.2.15-300.fc38.x86_64/3 /home/jimc/projects/lkp-tests.git/lib/data_store.rb:62:in `initialize': wrong number of arguments (given 2, expected 1) (ArgumentError) from /home/jimc/projects/lkp-tests.git/lib/common.rb:24:in `new' from /home/jimc/projects/lkp-tests.git/lib/common.rb:24:in `block in add_cached_method' from /home/jimc/projects/lkp-tests.git/lib/data_store.rb:246:in `create_new' from /home/jimc/projects/lkp-tests.git/lib/nresult_root.rb:241:in `create_layout' from /home/jimc/projects/lkp-tests.git/lib/nresult_root.rb:337:in `create_tables_layout' from /home/jimc/projects/lkp-tests.git/bin/run-local:167:in `<main>' any hints / guesses welcome !
On Fri, 19 May 2023 13:38:37 -0600, jim.cromie@gmail.com said:
hi all,
anyone familiar enough with running lkp-tests to recognize these errors ?
any hints / guesses welcome !
Did you already check all the embarrassingly obvious things like a file system being full and/or out of inodes, dangling symlinks that point to somewhere in the middle of the Indian Ocean, or a file system mounted R/O?
On Sat, May 20, 2023 at 11:02 PM Valdis Klētnieks <valdis.kletnieks@vt.edu> wrote:
On Fri, 19 May 2023 13:38:37 -0600, jim.cromie@gmail.com said:
hi all,
anyone familiar enough with running lkp-tests to recognize these errors ?
any hints / guesses welcome !
Did you already check all the embarrassingly obvious things like a file system being full and/or out of inodes, dangling symlinks that point to somewhere in the middle of the Indian Ocean, or a file system mounted R/O?
well, theres this in the readme, from 2022. # Note: lkp doesn't support ruby >= 3.0, default ruby version should be 2.x support is now improved/ing (fedora ships 3.2) and ruby 3.2 has been added to their test targets.
participants (2)
-
jim.cromie@gmail.com -
Valdis Klētnieks