-
Notifications
You must be signed in to change notification settings - Fork 259
fix: add code generation to run-unit-tests.stages #3985
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
Conversation
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.
Pull Request Overview
This PR adds missing code generation steps to the signed binary release pipeline. The change ensures that BPF code generation is performed during unit tests for the release pipeline, bringing it in sync with the existing PR pipeline configuration.
- Adds
make bpf-libandgo generate ./...commands to generate required BPF code - Synchronizes the signed binary release pipeline with the PR pipeline unit test configuration
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
|
/azp run Azure Container Networking PR |
|
Azure Pipelines successfully started running 1 pipeline(s). |
QxBytes
left a comment
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.
a883535
|
/azp run Azure Container Networking PR |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run Azure Container Networking PR |
|
Azure Pipelines successfully started running 1 pipeline(s). |
7c6ae83 to
58b57e4
Compare
|
/azp run Azure Container Networking PR |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Reason for Change:
We introduced bpf code as part of the iptables block binary, that relies on code generation. We updated run-unit-tests.yaml, which is used by the UT runs on the PR pipeline, to have the extra code generation steps. But the signed binary release uses run-unit-tests.stages.yaml, which wasn't updated. This PR adds the code generation to that file as well.
Issue Fixed:
Requirements:
Notes: