[email protected]

[publish-to-bcr-bot]

Release: https://github.com/yuyawk/rules_build_error/releases/tag/0.7.0

Automated by Publish to BCR

[bazel-io]

Hello @yuyawk, modules you maintain (rules_build_error) have been updated in this PR. Please review the changes.

[yuyawk]

@meteorcloudy
FYI, this new version 0.7.0 addresses your issue #3260

[bazel-io]

Hello @bazelbuild/bcr-maintainers, all modules in this PR have been approved by their maintainers. Please take a final look to merge this PR.

[meteorcloudy]

Please take a look at the build failure

Require module maintainers' approval for newly pushed changes.

[yuyawk]

Please take a look at the build failure

I did, but to be honest I have no idea about its cause. I'm not even sure if that's a persistent issue, or if that's triggered by the change in rules_build_error.
Mac OS usages are already tested with github-hosted runners and cannot reproduce the build error there, so I guess there's a gap between the buildkite environment and github-hosted runners.

With several versions rules_build_error has been tested with Mac OS, but this is the first time to see that /private/var/tmp/_bazel_buildkite (No such file or directory) error.

[bazel-io]

Hello @bazelbuild/bcr-maintainers, all modules in this PR have been approved by their maintainers. Please take a final look to merge this PR.

Require module maintainers' approval for newly pushed changes.

[bazel-io]

Hello @bazelbuild/bcr-maintainers, all modules in this PR have been approved by their maintainers. Please take a final look to merge this PR.