verilator@5.034#4341
Conversation
|
Hello @bazelbuild/bcr-maintainers, modules without existing maintainers (verilator) have been updated in this PR. |
2c0d26d to
3ae67e6
Compare
|
@bazel-io skip_check unstable_url |
|
FYI @hzeller |
hzeller
left a comment
There was a problem hiding this comment.
Nice!
I think @QuantamHD might be interested to have a look.
168d234 to
b11bade
Compare
|
@UebelAndre Thanks for all the fixes, to unblock this, you can comment |
|
For me this only blocks a migration to bzlmod but I'd rather not have to keep local patches for the issues identified in #4341 (comment). I'd rather wait for @jmillikin to review to avoid churn making |
|
@bazel-io skip_check incompatible_flags @meteorcloudy this build actually fails for a different reason and actually conforms to all incompatibility flags. FIY: |
|
Hmm, looks like the BUILD file was somehow changed? Let's retry the build first. |
|
I think this might be a weird bug in Bazel, I'm able to reproduce this locally by running bazel build twice. |
|
Although the content of is indeed confusing to bazel |
|
Let's wait for other reviewers to take a look then I can help merge it. |
|
@meteorcloudy looks like windows workers are also running into a similar issue. |
|
https://github.com/verilator/verilator/blob/master/ci/docker/run/hooks/build is confusing Bazel. @UebelAndre Let's add a .bazelignore file at the source root containing |
|
@UebelAndre Looks like windows doesn't work, feel free to remove |
|
@meteorcloudy this PR is good to go on my end. I leave the rest to you |
closes #3926