build: increase timeout for resultstore build uploads #20027
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
googlebot
added
the
cla: yes
We upload build results to Google Cloud `ResultStore`. Sometimes this seems to fail though and Bazel CI jobs exit red. This could be due to BES servers being slow, or servers being unreliably. Given that remote executors from GCP are behaving fine though, we try increasing the timeout first. We can disable the uploading if it doesn't get better.
devversion
force-pushed
the
build/disable-bes-results
branch
from
926dd19 to
614258e
Compare
devversion
added
merge safe
P3
andrewseguin
pushed a commit
that referenced
this pull request
Jul 17, 2020
We upload build results to Google Cloud `ResultStore`. Sometimes this seems to fail though and Bazel CI jobs exit red. This could be due to BES servers being slow, or servers being unreliably. Given that remote executors from GCP are behaving fine though, we try increasing the timeout first. We can disable the uploading if it doesn't get better. (cherry picked from commit 5026981)
ngwattcos
pushed a commit
to ngwattcos/components
that referenced
this pull request
Jul 20, 2020
We upload build results to Google Cloud `ResultStore`. Sometimes this seems to fail though and Bazel CI jobs exit red. This could be due to BES servers being slow, or servers being unreliably. Given that remote executors from GCP are behaving fine though, we try increasing the timeout first. We can disable the uploading if it doesn't get better.
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We upload build results to Google Cloud
ResultStore. Sometimes thisseems to fail though and Bazel CI jobs exit red. This could be due to
BES servers being slow, or servers being unreliably. Given that remote
executors from GCP are behaving fine though, we try increasing the
timeout first. We can disable the uploading if it doesn't get better.
For context: We upload to result store / source.cloud.google.com so that
CI builds with Bazel can be debugged better. e.g.
https://source.cloud.google.com/results/invocations/410a5790-54eb-43e8-96eb-c3cfa0f8960d