On Thu, Nov 18, 2021 at 5:41 AM Naresh Kamboju <naresh.kamboju@xxxxxxxxxx> wrote: ... > I have noticed intermittent failures on slow devices. ... > When the test runs more than X time (45 sec i guess) the script will > be killed by the runner script. In my test environment proc-uptime-001 seems to be passing ~40% (N=10) of the time, and taking approximately 0.60 seconds (~11 seconds / 18 tests). kselftest is not timing individual targets (maybe it should?), so I don't have a timing history but it used to pass 100% (N=60) of the time. > We will add this as known intermittent failure. Thanks, I'll remove it from my tests. Data for the numbers above: for X in $(seq 1 10) ; do echo $X && time make TARGETS="proc" kselftest | grep -P "ok.*proc-uptime-001" ; done 1 ok 10 selftests: proc: proc-uptime-001 real 0m10.605s user 0m3.427s sys 0m7.239s 2 not ok 10 selftests: proc: proc-uptime-001 # exit=134 real 0m10.808s user 0m3.237s sys 0m6.614s 3 ok 10 selftests: proc: proc-uptime-001 real 0m10.577s user 0m3.377s sys 0m7.269s 4 ok 10 selftests: proc: proc-uptime-001 real 0m12.424s user 0m3.215s sys 0m7.402s 5 not ok 10 selftests: proc: proc-uptime-001 # exit=134 real 0m11.101s user 0m3.257s sys 0m6.883s 6 not ok 10 selftests: proc: proc-uptime-001 # exit=134 real 0m10.797s user 0m3.199s sys 0m6.671s 7 not ok 10 selftests: proc: proc-uptime-001 # exit=134 real 0m12.817s user 0m3.308s sys 0m7.177s 8 not ok 10 selftests: proc: proc-uptime-001 # exit=134 real 0m10.816s user 0m3.201s sys 0m6.663s 9 not ok 10 selftests: proc: proc-uptime-001 # exit=134 real 0m10.832s user 0m3.145s sys 0m6.721s 10 ok 10 selftests: proc: proc-uptime-001 real 0m10.664s user 0m3.337s sys 0m7.375s
