-
Notifications
You must be signed in to change notification settings - Fork 1.1k
test: introduce cel-compat binary #4721
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
base: main
Are you sure you want to change the base?
Conversation
| secrets: inherit | ||
|
|
||
| # build the compatibility image for use in cross compatibility tests. | ||
| docker-compat-build: |
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.
we might actually need to move this into the same workflow as the test, so that the tests can depend on this image being built more easily, but that can happen in a followup, I don't want to re-structure workflows too much in this same PR.
| return runCompatibilityTests(ctx, client, args.skipGetRow) | ||
| } | ||
|
|
||
| func runCompatibilityTests(ctx context.Context, client *rpcclient.Client, skipGetRow bool) error { |
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.
I didn't make modifications to this, if anyone on the node team has more compatibility tests in mind, feel free to push to this branch or let me know what else needs to be tested. I was mainly focusing on how the image will be built and then how it will be utilized in future PRs.
This PR adds the compatibility testing binary that was being introduced in this PR #4680
By adding it in a single PR, we can more easily backport it to any branch that needs it.
For more context on its purpose see #4680 (review)