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

Issue 854038 link

Starred by 1 user
Status: Fixed
Owner:
mmoroz@chromium.org
Closed: Jun 2018
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

Flaky low coverage being reported since last week

Project Member Reported by mmoroz@chromium.org, Jun 19 2018 
2h timeout is too low for browser_tests binary, see https://chromium-coverage.appspot.com/reports/567214/linux/metadata/browser_tests.log for an example


ctrl+f "exit_code=124"

Comment 1 by mmoroz@chromium.org, Jun 19 2018

Summary: Flaky low coverage being reported since last week (was: Flaky low coverage reported since last week)

Comment 2 by mmoroz@chromium.org, Jun 19 2018 

It's literally less than the last hundred of testcases cannot finish in time.
Project Member

Comment 3 by bugdroid1@chromium.org, Jun 19 2018 

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

commit 956454ee88223fe7967bae7a13390a91b8ee3669
Author: Max Moroz <mmoroz@google.com>
Date: Tue Jun 19 03:05:52 2018

Comment 4 by mmoroz@chromium.org, Jun 19 2018

Status: Fixed (was: Started)
Should be fixed as of now, e.g. code-coverage-linux-0002 has successfully finished running browser_tests without any retries.
►

Sign in to add a comment