Skip to content

Conversation

@furtib
Copy link
Contributor

@furtib furtib commented Jan 16, 2026

Why:
We want the jenkins test's to pass

What:

  • Added the manual tag to all cc_*, compile_commands, codechecker_test targets (all of these are necessary for bazel test ... to pass)
  • Added debugging to the common base class for failing sub-processes
  • Added the flag for tests missing it
  • Bazel 6.2.1 (the Jenkins runner) does not support bzlmod even with the --enable_bzlmod flag, so I re-added the WORKSPACE file for the test.
  • The NFS has trouble deleting files. I set the cache for the external tests to be in their temporary folder.

Addresses:
Fixes: #123

@Szelethus Szelethus requested review from Szelethus and nettle January 16, 2026 13:22
Copy link
Contributor

@Szelethus Szelethus left a 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?

@furtib
Copy link
Contributor Author

furtib commented Jan 16, 2026

This is the only test where, no matter what we place in the .barzelrc, we must append this flag (or copy the .bazelrc).
Also, if we want to remove the flag from other tests, we should add this flag with build too, not just test.

@furtib furtib force-pushed the fix-jenkins branch 2 times, most recently from 986e1c0 to fe3b08f Compare January 16, 2026 14:38
.bazelrc Outdated
@@ -0,0 +1 @@
test --experimental_cc_implementation_deps
Copy link
Collaborator

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?

Copy link
Contributor Author

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

@furtib furtib force-pushed the fix-jenkins branch 3 times, most recently from d199e8a to 57add31 Compare January 21, 2026 12:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Bazel test is failing on current main: virtual_implementation_deps_include

3 participants