kselftest: Update kselftest results parser in test-definitions - Bad test result:

• Kselftest results-parser

  • Need to improve the speed of kselftest results parser functionality currently it is taking too long to parse

  • Kselftest arm64 following two and more test cases output is matching with TAP 13 format and but needs investigation to solve the problem. 

    • sve-ptrace

    • Za-ptrace

  • The fix could be test-definitions kselftest

    • Should be pass/fail/skip here we other pattern

      • <LAVA_SIGNAL_TESTCASE TEST_CASE_ID=arm64.syscall-abi.getpid() RESULT=SVE>

      • <LAVA_SIGNAL_TESTCASE TEST_CASE_ID=arm64.syscall-abi.sched_yield() RESULT=SVE>

      • <LAVA_SIGNAL_TESTCASE TEST_CASE_ID=arm64.tpidr2.skipped, RESULT=TPIDR2>

      • <LAVA_SIGNAL_TESTCASE TEST_CASE_ID=arm64.za-ptrace.Set RESULT=VL>

      • <LAVA_SIGNAL_TESTCASE TEST_CASE_ID=arm64.sve-ptrace.SVE RESULT=FPSIMD>

      • <LAVA_SIGNAL_TESTCASE TEST_CASE_ID=arm64.sve-ptrace.SVE RESULT=SVE_PT_VL_INHERIT>

    • Results_parser() in test-definitions to be fixed

Ref: LAVA job not parsing correctly:

Ref: LAVA job not parsing correctly:

Test results parser showing “Bad test results: “

Received signal: <TESTCASE> TEST_CASE_ID=arm64.sve-ptrace.SVE RESULT=FPSIMD
Bad test result: FPSIMD
<LAVA_SIGNAL_TESTCASE TEST_CASE_ID=arm64.sve-ptrace.SVE RESULT=FPSIMD>
Received signal: <TESTCASE> TEST_CASE_ID=arm64.sve-ptrace.SVE RESULT=get_fpsimd()
Bad test result: get_fpsimd()
<LAVA_SIGNAL_TESTCASE TEST_CASE_ID=arm64.sve-ptrace.SVE RESULT=get_fpsimd()>
Received signal: <TESTCASE> TEST_CASE_ID=arm64.sve-ptrace.SVE RESULT=SVE_PT_VL_INHERIT
Bad test result: SVE_PT_VL_INHERIT
<LAVA_SIGNAL_TESTCASE TEST_CASE_ID=arm64.sve-ptrace.SVE RESULT=SVE_PT_VL_INHERIT>
Received signal: <TESTCASE> TEST_CASE_ID=arm64.sve-ptrace.SVE RESULT=SVE_PT_VL_INHERIT
Bad test result: SVE_PT_VL_INHERIT
<LAVA_SIGNAL_TESTCASE TEST_CASE_ID=arm64.sve-ptrace.SVE RESULT=SVE_PT_VL_INHERIT>
Received signal: <TESTCASE> TEST_CASE_ID=arm64.sve-ptrace.Set RESULT=SVE
Bad test result: SVE
<LAVA_SIGNAL_TESTCASE TEST_CASE_ID=arm64.sve-ptrace.Set RESULT=SVE>
<LAVA_SIGNAL_TESTCASE TEST_CASE_ID=arm64.sve-ptrace.Set RESULT=and>
Received signal: <TESTCASE> TEST_CASE_ID=arm64.sve-ptrace.Set RESULT=and
Bad test result: and
Received signal: <TESTCASE> TEST_CASE_ID=arm64.sve-ptrace.Set RESULT=and
Bad test result: and

And few more test cases are having this problem,

Bad test result: Result
<LAVA_SIGNAL_TESTCASE TEST_CASE_ID=clone3.clone3_set_tid.[1710] RESULT=Result>
Received signal: <TESTCASE> TEST_CASE_ID=clone3.clone3_set_tid.[1710] RESULT=Result
Bad test result: Result
<LAVA_SIGNAL_TESTCASE TEST_CASE_ID=clone3.clone3_set_tid.PIDs RESULT=in>
Received signal: <TESTCASE> TEST_CASE_ID=clone3.clone3_set_tid.PIDs RESULT=in
Bad test result: in