workflow: add 6.1 and 6.3 kernels #3069
Merged
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
|
Error: GitHub self host service had an infrastructure issue, Infra team has been updated and are now checking the issue. |
1 similar comment
|
Error: GitHub self host service had an infrastructure issue, Infra team has been updated and are now checking the issue. |
- will add 6.1 and 6.3 workflows once they're fixed
|
Im only including the DEBUG SHELL for 6.1 and 6.3 kernels in this PR so I can further investigate why tracee is failing in those kernels (and enable the PR workflow for them once they're fixed). I need to merge this orelse the debug shell workflow won't work and I won't be able to investigate. |
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.
@yanivagman FYI, IMO would be good to have those included (and any issue fixed, like #3067, before the 0.14.1).
These are 6.1 and 6.3 kernels from the upstream stable tree, being used in Ubuntu Jammy, and using the same kconfig values as Ubuntu does for 5.19 kernels (this way we can test upstream trees before Ubuntu releases them).