-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Unbounded thread pool in ByteStreamBuildEventArtifactUploader #6806
Comments
ulfjack
added
type: bug
P1
I'll work on this now. (Assignee required)
release blocker
labels
Nov 30, 2018
@meteorcloudy has a patch at: |
For reference, the unbounded thread pool is located at: bazel/src/main/java/com/google/devtools/build/lib/remote/ByteStreamBuildEventArtifactUploader.java Line 45 in 48b672c
|
@ulfjack Do you want me to submit this change? |
Yes, ASAP. |
:-D |
laurentlb
pushed a commit
that referenced
this issue
Dec 14, 2018
Fixes #6806 RELNOTES: None PiperOrigin-RevId: 223763834
laurentlb
pushed a commit
that referenced
this issue
Dec 17, 2018
Fixes #6806 RELNOTES: None PiperOrigin-RevId: 223763834
luca-digrazia
pushed a commit
to luca-digrazia/DatasetCommitsDiffSearch
that referenced
this issue
Sep 4, 2022
This is a follow up for bazelbuild/bazel@7fc967c, related issue bazelbuild/bazel#6806 RELNOTES: None PiperOrigin-RevId: 223944430
luca-digrazia
pushed a commit
to luca-digrazia/DatasetCommitsDiffSearch
that referenced
this issue
Sep 4, 2022
Fixes bazelbuild/bazel#6806 RELNOTES: None PiperOrigin-RevId: 223763834
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It's possible that this is causing our CI to be flaky.
The text was updated successfully, but these errors were encountered: