On Tue, 30 Apr 2019 at 09:19, Remi Duraffort remi.duraffort@linaro.org wrote:
Hello,
I'm surprised by such change as the corresponding source code hasn't been touched for more than a year. Anyway, I can confirmed that the result strings should be lower case "pass", "fail", "skip" or "unknown".
Isn't this caused by removal of default 'fixup' dictionary? I recall talking about that recently.
milosz
Thanks
Le mer. 24 avr. 2019 à 12:15, Patryk Mungai Ndungu patryk.mungai-ndungu.kx@renesas.com a écrit :
Hello,
I have recently upgraded from 2018.11 to 2019.03 and have noticed that the results of a lot of the tests I have been running no longer got parsed correctly by LAVA. This was because I was sending the results using upper case results strings. Eg. lava-test-case <test-case> PASS opposed to lava-test-case <test-case> pass
This resulted in the following logs in the lava job: Received signal: <TESTCASE> TEST_CASE_ID=ETH_T_001 RESULT=PASS Bad test result: PASS
Changing my results parsing script to only send lower case results strings fixed the issue, but was this restriction intended with the upgrade?
Kind Regards, Patryk
Lava-users mailing list Lava-users@lists.lavasoftware.org https://lists.lavasoftware.org/mailman/listinfo/lava-users
-- Rémi Duraffort LAVA Team, Linaro _______________________________________________ Lava-users mailing list Lava-users@lists.lavasoftware.org https://lists.lavasoftware.org/mailman/listinfo/lava-users