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
.github/workflows: re-enable coverage in BPF tests #23291
Conversation
c013ee7
to
e989f2b
Compare
/cc @dylandreimerink Looks like CoverBee is panic'ing in a different place now: https://github.com/cilium/cilium/actions/runs/3996735051/jobs/6857147501
|
This pull request has been automatically marked as stale because it |
blocked on #24094 |
c084a2f
to
570db59
Compare
BPF tests passed with test commit and #24094 pulled in: https://github.com/cilium/cilium/actions/runs/4302018934 Removing test commit and marking as ready for review. |
570db59
to
d37f1d7
Compare
d37f1d7
to
8cfa043
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The related job is skipped in this PR (as there is no bpf change), however, I have verified locally, so it's safe to merge. https://github.com/cilium/cilium/actions/runs/4304772254/jobs/7506267906 |
@sayboras FWIW this was also successfully run with a test commit that triggered the respective test, see #23291 (comment) |
oops my bad 💯 |
With the recent CoverBee version bump in commit a38fa32 ("vendor: Bumped CoverBee to v0.3.0 and cilium/ebpf to v0.10.0") we can enable coverage reporting for BPF tests again.
This reverts commit edd2abf (".github/workflows: disable coverage in BPF tests").
Fixes #22088