New issue
Advanced search Search tips

Issue 662929 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 676196
Owner: ----
Closed: Dec 2016
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug

Blocking:
issue 621599



Sign in to add a comment

[W3C auto-import] w3c-test-autoroller added failure lines instead of rebaselining.

Project Member Reported by qyears...@chromium.org, Nov 7 2016

Issue description

In http://crrev.com/2477133002/, w3c-test-autoroller added [ Failure ] lines instead of new baselines for testharness tests.

This was fixed by tkent in http://crrev.com/2483763002/.

Build: https://build.chromium.org/p/chromium.infra.cron/builders/w3c-test-autoroller/builds/7780

What I expected to happen, was that update-w3c-test-expectations was supposed to download baselines at: https://cs.chromium.org/chromium/src/third_party/WebKit/Tools/Scripts/webkitpy/w3c/update_w3c_test_expectations.py?sq=package:chromium&dr&l=335

Making the logging more verbose may make it easier to solve issues like this in the future.
 
Mergedinto: 676196
Status: Duplicate (was: Available)
Summary: [W3C auto-import] w3c-test-autoroller added failure lines instead of rebaselining. (was: w3c-test-autoroller added failure lines instead of rebaselining.)
Looking at that original issue again, some of those tests were originally marked [ Slow ], so I believe that this is probably the same issue as  bug 676196 .

Sign in to add a comment