Hi all,
I run into some unexpected behavior when it comes to LAVA job IDs reported by the "lavacli jobs sumit" command for multi node tests.
What I get is a list of newline separated job IDs like:
lavacli jobs submit <my-job-description> 132.0 132.1
To my understanding this tries to express that 132.1 is a sub job of 132. OK, but this is a problem if I now try to download the junit report for the second job (=132.1).
It seems 132.1 is not a valid job ID (API wise), it has to be translated to 133 to work properly.
This is still doable, but I'm unsure if I can relay on 133 really being the 132.1 job in case there are several job submissions at the same time.
Is that a bug of lavacli? What is the reasoning for returning a sub job ID which seems to be invisible to the rest of the LAVA infrastructure / API?
I'm currently running lavacli 1.2-1, as shipped by Debian 12.
Any input welcome...
Best regards, Florian