New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 848834 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Aug 30
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug

Blocking:
issue 759794



Sign in to add a comment

Bots: do not upload new reports info when everything seems broken

Project Member Reported by mmoroz@chromium.org, Jun 1 2018

Issue description

We probably still should upload something to flag that there might be an error happening on the bots.

The idea came to me after  issue 848803 . Basically, none of the targets can be built, so the bot only uploads build logs + new_report_info file for that. That leads to "too many reports uploaded" cron error.

Might be not necessary though, if we find another way to detect bad revisions and avoid them.
 
Blocking: 759794
Owner: mmoroz@chromium.org
Status: Fixed (was: Untriaged)
This shouldn't happen anymore since https://chrome-internal-review.googlesource.com/c/chrome/tools/code-coverage/+/642431 and some more recent fixes like https://chrome-internal.googlesource.com/chrome/tools/code-coverage/+/9b1be5a40c5b169800b68b28ef7a9fda57c7be47

Sign in to add a comment