Skip to content

src: lava_callback: handle artifacts uploaded from test jobs #1141

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 28, 2025

Conversation

a-wai
Copy link
Contributor

@a-wai a-wai commented May 6, 2025

Test jobs might need to upload artifacts directly from LAVA (this is needed e.g. for GCOV data when checking for code coverage), but we currently have no way to add those artifacts to the corresponding node.

Add such a feature in a rather generic way, so jobs can provide both the artifact name and its URL through a specially-formatted result entry:

artifact-upload:<artifact name>:<artifact URL>

Therefore, all test results starting with artifact-upload: will be processed and stored in the corresponding node's artifacts dict, with <artifact name> being the entry key and <artifact URL> being its value.

Depends on #1159 & kernelci/kernelci-core#2878

@tollsimy
Copy link

tollsimy commented May 6, 2025

Hi @a-wai could it be solved by #1140 ?
We added a way to introduce input artifacts in kernelci/kcidb-io#99, but I am not sure it will fix your issue.

@a-wai
Copy link
Contributor Author

a-wai commented May 7, 2025

Hi @tollsimy!
No, this is a vastly different issue I'm trying to address: #1140 retrieves input files from jobs by looking at the deploy actions, while this PR retrieves output files that are generated during the tests, created and uploaded by the DUT.

@tollsimy
Copy link

tollsimy commented May 7, 2025

@a-wai Got it, that makes sense, thanks!

@nuclearcat
Copy link
Member

Is it tested anyhow, or maybe how i can help with testing?

@a-wai
Copy link
Contributor Author

a-wai commented May 13, 2025

@nuclearcat only manually tested for now, we should have more results soon now that I've (hopefully) fixed #1131

@a-wai a-wai force-pushed the lava-callback-handle-artifacts branch 2 times, most recently from 57ceeed to 34c8774 Compare May 15, 2025 15:32
@a-wai a-wai marked this pull request as draft May 15, 2025 15:32
@a-wai a-wai force-pushed the lava-callback-handle-artifacts branch 4 times, most recently from 4d75674 to 9bf2dcb Compare May 16, 2025 14:49
Test jobs might need to upload artifacts directly from LAVA (this is
needed e.g. for GCOV data when checking for code coverage), but we
currently have no way to add those artifacts to the corresponding node.

Add such a feature in a rather generic way, so jobs can provide both the
artifact name and its URL through a specially-formatted result entry:

  artifact-upload:<artifact name>:<artifact URL>

Therefore, all test results starting with `artifact-upload:` will be
processed and stored in the corresponding node's `artifacts` dict, with
`<artifact name>` being the entry key and `<artifact URL>` being its
value.

Signed-off-by: Arnaud Ferraris <[email protected]>
@a-wai a-wai force-pushed the lava-callback-handle-artifacts branch from 9bf2dcb to a4b7119 Compare May 21, 2025 09:08
@a-wai
Copy link
Contributor Author

a-wai commented May 21, 2025

Coverage data successfully retrieved on the latest staging run, see this node for an example.

@a-wai a-wai marked this pull request as ready for review May 21, 2025 13:07
@a-wai a-wai added this pull request to the merge queue May 28, 2025
Merged via the queue into kernelci:main with commit 2066052 May 28, 2025
4 checks passed
@a-wai a-wai deleted the lava-callback-handle-artifacts branch May 28, 2025 07:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants