ci: In "Tetragon Go Test" add vmlinux in artifact when test fails #3526
+8
−0
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kkourt
reviewed
Mar 21, 2025
Kprobe are not extactly the same between arm and x86_64. So to help understand why some tests fails on one side and not the other, it can be helpful to use the vmlinux directly from the CI instead of deploying a specific VM with the same architecture to debug Signed-off-by: Tristan d'Audibert <[email protected]>
ScriptSathi
force-pushed
the
pr/ScriptSathi/add-vmlinux-workflow
branch
from
6ecf9a5 to
5b40d47
Compare
✅ Deploy Preview for tetragon ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
To help debugging between arch, I think it is a great idea to upload the vmlinux file when this test fails
This will help fixing #3492
Motivation
TestSpecsusesksys_lseeksymbol which is inlined (I think) on ARM but not on x86_64. If we upload the vmlinux, we can load the BTF spec and check what hooks are shared#3414 (comment)
Description
Kprobes are not exactly the same between ARM and x86_64. To help understand why some tests fail on one architecture and not the other, it can be helpful to use the vmlinux file directly from the CI instead of deploying a specific VM with the same architecture for debugging.