Pawan,

I think you're confusing 2 different things. Job status only says if
all actions in the job completed successfully. For example if your
test script runs for too long, lava will call a timeout and end the
job as 'incomplete'. Similarly if your infrastructure doesn't work
properly (power_on command doesn't power the device on, etc). On the
other hand test results can have 4 values: pass, fail, skip, unknown.
The last one is only telling that something went wrong with data
collection.

To sum up, failed test doesn't mean that the test job is incomplete.
These are statuses of 2 different things.

Best Regards,
Milosz

On Wed, Feb 7, 2024 at 4:08 AM pawanKumar <pawan4749@gmail.com> wrote:
>
> Hi Team,
>
> I was running the lava jobs and I found a difference in the status after job completion with failures. There were failures in
> i) The interactive test and lava overlay test [cases] but still the status of the job shows as "COMPLETE".
> ii) I tried an action failure retry, when action failure for the first time, it shows the result as failure but job status as complete. The retry- failure status should be ignored if it fails for the first time. I convert the test results into JUNIT using rest api. In the junit result it displays failure for the test case.
> My question is, How can we customize the status of the job or ignore the test result in case of failure-retry?
> Any Advice please.
>
>
>
> Best Regards
> Pavan Kumar
> _______________________________________________
> lava-devel mailing list -- lava-devel@lists.lavasoftware.org
> To unsubscribe send an email to lava-devel-leave@lists.lavasoftware.org