Fix bzlmod CI failure by loading cc_binary#638
Conversation
Very surprising that this didn't fail before, as apparently this load statement was always needed for bzlmod. It started failing in #637 --- and, interestingly, only on a _second_ commit. Still, the fix is straightforward.
Should we make a change to the github actions workflow to catch this class of errors? |
That's the weird thing. It did catch this error! But for whatever reason, it didn't seem to catch it until several commits after the original error had landed. We saw something similar with several of the bazel changes in the migration to bzlmod. I think |
Very surprising that this didn't fail before, as apparently this load
statement was always needed for bzlmod. It started failing in #637 ---
and, interestingly, only on a second commit. Still, the fix is
straightforward.