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

Issue 921300 link

Starred by 1 user

Issue metadata

Status: Untriaged
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Correctly handle test results and display failed tests

Project Member Reported by liaoyuke@chromium.org, Jan 12

Issue description

This would be important for both us and developers when investigating why coverage number is incorrect.
 
Project Member

Comment 1 by bugdroid1@chromium.org, Jan 15

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/tools/build/+/5ecb47156270b05c80bd25f0684a7e81bfb754fb

commit 5ecb47156270b05c80bd25f0684a7e81bfb754fb
Author: Yuke Liao <liaoyuke@chromium.org>
Date: Tue Jan 15 03:09:04 2019

[code coverage] Work around fuzzer invalid test results

There on more than 300 fuzzer targets and all of them are failing due
to invalid test results, and the 300+ red steps cause the whole build
to fail as a Infra failure, which is not good because it masks the real
failed steps.

This CL works the issue around with a temporary solution.

Bug: 921300
Change-Id: I78d7c9cb0c7550fe6c70f42f50cd1512a3fb1c36
Reviewed-on: https://chromium-review.googlesource.com/c/1409704
Reviewed-by: Shuotao Gao <stgao@chromium.org>
Commit-Queue: Yuke Liao <liaoyuke@chromium.org>

[modify] https://crrev.com/5ecb47156270b05c80bd25f0684a7e81bfb754fb/scripts/slave/recipe_modules/clang_coverage/resources/merge_profiles.py

Sign in to add a comment