Jeremy Kun

I was able to remove mlir-opt, which helped (in particular, removing all the code in `mlir/test` from the dependencies), but it seems the next hurdle is that a lot of...

As of now, https://github.com/google/heir/pull/895 has a wallclock time of 25 minutes, which is... an improvement I guess.

Without removing the use of mlir-cpu-runner, I don't think we'll be able to do much more here. Closing.

Bazel just defines build targets and figures out all the dependencies you need when you attempt to build a target. I think one of the issues here is that some...

> If we switch to `-c opt` build for all test, the critical path can be much shorter as the critical path is often `tests/Transforms/heir_vectorizer/box_blur`. Definitely we should deduplicate if...

Testing at 651047045d870879cf12d5fa4827af4f2dc6c322 (including fresh download of all dependencies) ``` # cold start bazel clean --expunge time bazel test -c opt //...:all 43:43.44 total # incremental build # make a...

After discussing with the bazel maintainers internally, the issue is that when you build a target that is used in another bazel rule (e.g., building a compiler to compile some...

I think https://github.com/google/heir/issues/1504 is the remainder of work for this issue, so closing.

I think the most recent push of the PDLL article might have landed the tutorial at a bad upstream LLVM commit hash. I cannot reproduce this myself but I see...

ah I see the problem. The CMake build added the `externals` directory, which is conflicting with the glob in `bazel build ...:all` because the external LLVM from that directory includes...