-
Notifications
You must be signed in to change notification settings - Fork 3
Fix jenkins testing #143
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?
Fix jenkins testing #143
Conversation
Szelethus
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.
Are both the .bazelrc and the test changes required?
|
This is the only test where, no matter what we place in the |
986e1c0 to
fe3b08f
Compare
.bazelrc
Outdated
| @@ -0,0 +1 @@ | |||
| test --experimental_cc_implementation_deps | |||
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.
Can we avoid adding .bazelrc ?
Is it possible to add --experimental_cc_implementation_deps only to tests which test implementation_deps?
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.
It seems like adding a manual tag to the cc_* targets themselves is enough to circumvent the use of the flag.
I have removed the .bazelrc file
d199e8a to
57add31
Compare
Why:
We want the jenkins test's to pass
What:
cc_*,compile_commands,codechecker_testtargets (all of these are necessary for bazel test ... to pass)--enable_bzlmodflag, so I re-added the WORKSPACE file for the test.Addresses:
Fixes: #123