Permission to read LAVA job logs by anonymous user
Description
Environment
Engineering Progress Update
Fix the broken links in test_summary.html
Attachments
- 04 Nov 2021, 08:09 AM
- 04 Nov 2021, 08:07 AM
Activity

Xinyu Zhang September 5, 2022 at 4:03 AM
Patch merged. Thanks Arthur for the fix!

Arthur She September 3, 2022 at 1:01 AM
Xinyu mentioned the target_log.txt is what they want and also mentioned there are some broken links in the test_summary.html.
I’ve pushed a patch to fix that.

Arthur She August 29, 2022 at 4:59 AM
Hi @Anton Komlev , @Xinyu Zhang ,
After checking the code, I found the tf-m-build-and-test job has already retrieved the LAVA test log and saved it as target_log.txt under the cfgs directory of the build artifacts.
Is that what you want?

Arthur She August 24, 2022 at 3:55 PM
I’ve confirmed with Xinyu that the requirement is to retrieve the FVP LAVA test log and save it to the build job artifacts

Anton Komlev August 16, 2022 at 1:20 PMEdited
The ticket is reopened because anonymous access to FVP output logs became essential. TF-M wants test patches on FVP only and those logs are the only source of output information for developers.
Note:
Read permission to LAVA for anonymous users is not the goal while access to FVP test output logs is. The valid alternative is to copy the logs to already accessible location like Jenkins artefacts (suppose TF-A uses that way)
Details
Details
Assignee

Reporter

Anonymous users have no permission to read LAVA job logs, which is inconvenient for them to check the test results by Allow CI. Could you please help to add read permission for anonymous users?
BTW, LAVA job submitted by Staging CI is accessible to anonymous users.