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

Issue 870484 link

Starred by 2 users
Status: Fixed
Owner:
mmoroz@chromium.org
Closed: Aug 7
Cc:
█ robert...@chromium.org
liaoyuke@chromium.org
mmoroz@chromium.org
infe...@chromium.org
st...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug



Sign in to add a comment

Bots: "too low coverage reported" seems to happen too often

Project Member Reported by mmoroz@chromium.org, Aug 2 
https://pantheon.corp.google.com/errors/CPHL8Z6A9-aiBQ?time=P7D&project=chromium-coverage&organizationId=433637338589

13 times in the past 7 days

I've quickly inspected the logs and haven't seen any problem. Will investigate more.
Project Member

Comment 1 by bugdroid1@chromium.org, Aug 3 

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chrome/tools/code-coverage/+/1d2164a563ddcbbd1eadf0802b80e35d10f88331

commit 1d2164a563ddcbbd1eadf0802b80e35d10f88331
Author: Max Moroz <mmoroz@google.com>
Date: Fri Aug 03 19:00:32 2018

Comment 2 by mmoroz@chromium.org, Aug 3 

So the problem was that some bots stuck on an old revision and could not pull new changes. One bot had stuck because it's /tmp diff exhausted the disk space.

I've added some additional clean up + a restart after every 10 loops so that if ever bots get into an inconsistent state, they should be able to recover automatically, unless they hang completely. We'll see how it goes.

Comment 3 by mmoroz@chromium.org, Aug 7

Status: Fixed (was: Started)
No errors reported in the last 4 days.
►

Sign in to add a comment