Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[5.1] Bazel crashes with InterruptedException when certain benign errors happen #14932

Closed
bazel-io opened this issue Mar 2, 2022 · 2 comments

Comments

@bazel-io
Copy link
Member

bazel-io commented Mar 2, 2022

Forked from #14787

@bazel-io bazel-io added this to the 5.1 release blockers milestone Mar 2, 2022
@gregestren
Copy link
Contributor

@Wyverald what's the right way to triage a 5.1 bug?

@Wyverald
Copy link
Member

Wyverald commented Mar 8, 2022

@gregestren I think "ignore" would be fine, but I don't know what our tooling currently works with. If leaving an issue unlabeled is hard to work with, we could repurpose the "release blocker" label to mean "this is to track a bug for a release, don't triage".

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

No branches or pull requests

3 participants