-
Notifications
You must be signed in to change notification settings - Fork 24
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
ROX-18679: containerize integration tests #1357
ROX-18679: containerize integration tests #1357
Conversation
Skipping CI for Draft Pull Request. |
|
6a48d14
to
9129aef
Compare
7d1f1a8
to
a5bea14
Compare
553ca12
to
3b2e835
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.
Looks good! This should save as some headaches!
if: ${{ !contains(github.event.pull_request.labels.*.name, 'skip-integration-tests') }} | ||
# Temporarily disable benchmarks due to baseline calculation | ||
# inconsistencies. This will be fixed and re-enabled in the future. | ||
if: false # ${{ !contains(github.event.pull_request.labels.*.name, 'skip-integration-tests') }} |
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.
This could probably be done in a separate PR, it'd be merged much faster I'd assume.
Running integration tests locally worked for me
TestRepeatedNetworkFlow failed, but it always fails for me. |
85565fe
to
ae6e3b1
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.
Looks good to me. One minor question due to my lack of golang details -- I see that the original version was building the test binary specifying GOARCH & GOOS, and now we don't do that. Does it impact anything?
Since we're using buildx to build multi-arch images, all of this is handled by Go implicitly, at least in the sense that it's building a 'native' binary for each platform (via qemu) |
Description
Containerize the integration tests, to bundle common dependencies and files. Now that we're running on the test host, containerizing the tests will make it easier to create test bundles and traceable artifacts for each build/test run.
Checklist
Automated testing
If any of these don't apply, please comment below.
Testing Performed
Images built locally, but relying on CI for additional testing of multi-arch builds and end-to-end use of the resulting images.