lava: Make the AUM tests logs work again the web UI
Commit 39e6ec4f made tar output the extracted filenames while
deployng the overlays and later commit 39e6ec4f made it
customizable since the AUM tests do many reboot cycles each with their
own (redundant) overlay deployment, causing the logs to grow massively
and going over the limits imposed by the LAVA web UI, which refuses to
display them and only offers to download them in JSON format.
Unfortunately the fix on 39e6ec4f worked only partially and the overlays in the loop were still upacked in verbose mode, resulting in unreadable logs.
For some reason that currently escapes me related to the way Jinja2 imports work, re-importing the template with the macros from the looping template fixes the issue.
Tasks: T7573
Merge request reports
Activity
@em that's very interesting -- with your patch my
lqaversion is not able to submit the generated job:Submitting job aum-ota-api.yaml: <Fault 400: 'Problem with submitted job data: Loading job submission failed: while parsing a block mapping\n in "<unicode string>", line 2, column 1\ndid not find expected key\n in "<unicode string>", line 152, column 1.'>I'am using the build/work environment based on Apertis v2022dev1, however I did not updated it for a while.
-
Did an update of the container to the most recent version -- still have the error with this string in my test job:
Submitting job aum-ota-api.yaml: <Fault 400: 'Problem with submitted job data: Loading job submission failed: while parsing a block mapping\n in "<unicode string>", line 2, column 1\ndid not find expected key\n in "<unicode string>", line 152, column 1.'>And have no any issue if I revert that commit
Hah, it fails on the CI as well. :/
enabled an automatic merge when the pipeline for 0dc36df3 succeeds
