bpftrace-compiler: add vendoring#5877
Conversation
0bd8a59 to
05f778d
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #5877 +/- ##
==========================================
- Coverage 19.52% 17.12% -2.41%
==========================================
Files 19 474 +455
Lines 3021 85606 +82585
==========================================
+ Hits 590 14661 +14071
- Misses 2310 69429 +67119
- Partials 121 1516 +1395 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
@christoph-zededa , go-tests passed. Is this a good indication that it works? Can we mark the PR as ready for review? |
hopefully this helps against flakiness of the CI as we
experience sometimes the following error:
```
27 [bpftrace 16/17] RUN CGO_ENABLED=0 GOARCH=${TARGETARCH} go build -o /bpftrace-helper
27 0.634 go: downloading github.com/pmorjan/kmod v1.1.1
27 0.637 go: downloading golang.org/x/sync v0.16.0
27 2.134 go: downloading golang.org/x/sys v0.35.0
coverage: 26.6% of statements
panic: test timed out after 5h0m0s
running tests:
TestCurrentKernels (4h24m51s)
```
Signed-off-by: Christoph Ostarek <christoph@zededa.com>
05f778d to
753c643
Compare
|
/rerun red |
I also added the vendor files for bptrace-compiler, not only the tool that is used by bpftrace-compiler. |
|
Happy to see Yetus green for a PR with more than 3k files! |
|
And Go-Tests green as well, of course! |
Description
hopefully this helps against flakiness of the CI as we experience sometimes the following error:
How to test and validate this PR
Run tests on our CI repeatedly and not experiencing the above issue.
Changelog notes
Internal improvement for our CI.
PR Backports
For all current LTS branches, please state explicitly if this PR should be
backported or not. This section is used by our scripts to track the backports,
so, please, do not omit it.
Here is the list of current LTS branches (it should be always up to date):
Also, to the PRs that should be backported into any stable branch, please
add a label
stable.Checklist
And the last but not least:
check them.
Please, check the boxes above after submitting the PR in interactive mode.