Skip to content
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

Update GitHub matrix to use correct 6.1.x kernel #2004

Merged

Conversation

ddelnano
Copy link
Member

@ddelnano ddelnano commented Sep 4, 2024

Summary: Update GitHub matrix to use correct 6.1.x kernel

Builds after #1995 would fail since GitHub would attempt to run the 6.1.8 kernel build, which bazel no longer understands. This also updates the qemu test runner kernel that was incorrectly updated in #1999. I thought I had exercised that default value with my testing, but it didn't trigger that default value.

Relevant Issues: N/A

Type of change: /kind bugfix

Test Plan: GitHub build on #2002 which pulls in the matrix change is no longer failing

Signed-off-by: Dom Del Nano <[email protected]>
(cherry picked from commit 348d850)
@ddelnano ddelnano requested a review from a team as a code owner September 4, 2024 14:44
@ddelnano ddelnano merged commit 9ae53a8 into pixie-io:main Sep 4, 2024
30 checks passed
@ddelnano ddelnano deleted the ddelnano/fix-github-matrix-default-kernels branch September 4, 2024 15:58
ddelnano added a commit to ddelnano/pixie that referenced this pull request Sep 23, 2024
Summary: Update GitHub matrix to use correct 6.1.x kernel

Builds after pixie-io#1995 would fail since GitHub would attempt to run the
6.1.8 kernel build, which bazel no longer understands. This also updates
the qemu test runner kernel that was incorrectly updated in pixie-io#1999. I
thought I had exercised that default value with my testing, but it
didn't trigger that default value.

Relevant Issues: N/A

Type of change: /kind bugfix

Test Plan: GitHub build on pixie-io#2002 which pulls in the matrix change is no
longer failing

GitOrigin-RevId: 9ae53a8
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.

2 participants