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

Issue 741822 link

Starred by 2 users

Issue metadata

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



Sign in to add a comment

Error messages from pre-cq are useless

Project Member Reported by nsanders@chromium.org, Jul 12 2017

Issue description


What steps will reproduce the problem?
(1) Use commit queue
(2) pre-cq or cq usually fails 
(3) Error is typically "VMTests failed with Error 1", this is probably your fault
(4) It's never my fault
(5) Difficult to tell why "Error 1" occurred.

What is the expected result?
CQ failures should state which test failed. 
Flake tests should not block CQ.

What happens instead?
Time wasted digging though tons of logspam, to discover CQ failed due to known flake test (https://bugs.chromium.org/p/chromium/issues/detail?id=741110)


Please use labels and text to provide additional information.


For graphics-related bugs, please copy/paste the contents of the about:gpu
page at the end of this report.

 
Owner: nsanders@chromium.org
Please link to a specific occurrence.
Owner: akes...@chromium.org
https://chromium-review.googlesource.com/#/c/564306/
Cc: nxia@chromium.org pho...@chromium.org
Labels: Hotlist-Fixit
Owner: ----
Status: Available (was: Untriaged)
Usability improvements here should result from where's-my-cl and from cl-unrejector.
Components: Infra>Client>ChromeOS>CI
Components: -Infra>Client>ChromeOS

Comment 6 by nxia@chromium.org, Jun 8 2018

Cc: -nxia@chromium.org

Sign in to add a comment