New issue
Advanced search Search tips

Issue 817025 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: May 2018
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

[WPT Import] Importer does not handle CQ+2 failures correctly

Project Member Reported by robertma@chromium.org, Feb 27 2018

Issue description

When an import CL passes CQ dry run but fails to be submitted (e.g. last-minute merge conflicts), importer doesn't see the failures and considers the import successful (which then leads to bugs to be filed by the notifier, even though nothing is imported).
 
Labels: -Pri-3 Pri-2
Owner: robertma@chromium.org
Status: Assigned (was: Available)
Bumping to P2 as this has happened again within the week. And it should be easy to fix :)
Do you have an update @robertma :)
Project Member

Comment 4 by bugdroid1@chromium.org, May 30 2018

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/1e665d5f61e0558ef0b3dfe5029152f237ad9618

commit 1e665d5f61e0558ef0b3dfe5029152f237ad9618
Author: Robert Ma <robertma@chromium.org>
Date: Wed May 30 21:39:41 2018

[WPT import] Handle CQ+2 failures

Sometimes CQ+2 can fail even when CQ+1 succeeds (e.g. last-minute merge
conflicts). This CL catches this failure properly.

Bug:  817025 
Change-Id: Ic6679a7b4797132abd3ecae348644d6e14f73c7c
Reviewed-on: https://chromium-review.googlesource.com/1079889
Reviewed-by: Quinten Yearsley <qyearsley@chromium.org>
Commit-Queue: Robert Ma <robertma@chromium.org>
Cr-Commit-Position: refs/heads/master@{#563007}
[modify] https://crrev.com/1e665d5f61e0558ef0b3dfe5029152f237ad9618/third_party/blink/tools/blinkpy/w3c/test_importer.py
[modify] https://crrev.com/1e665d5f61e0558ef0b3dfe5029152f237ad9618/third_party/blink/tools/blinkpy/w3c/test_importer_unittest.py

Status: Fixed (was: Assigned)

Sign in to add a comment