New issue
Advanced search Search tips

Issue 709410 link

Starred by 1 user
Status: Duplicate
Merged: issue 709028
Owner: ----
Closed: Aug 2017
Cc:
panicker@chromium.org
yoavweiss@chromium.org
npm@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

virtual/mojo-loading/http/tests/w3c/webperf/submission/Intel/user-timing/test_user_timing_clearMarks.html failing

Project Member Reported by jkrcal@chromium.org, Apr 7 2017 
The test has been flaky for some time, started failing much more often on Thu April 06, around 10pm GMT.

Culprit / owner is not clear > for Blink triage.

I will disable the test soon as an instant remedy.

Comment 2 by jkrcal@chromium.org, Apr 7 2017 

I am puzzled about the test expectations: this test has Failure expectation.

What is wrong with it? Why does it ever appear on the sheriff-o-matic dashboard?

Comment 3 by dglazkov@chromium.org, Apr 13 2017

Components: -Blink Blink>PerformanceAPIs
Labels: -Pri-2 Pri-3
Routing to Web perf team.

Comment 4 by tdres...@chromium.org, Jul 31 2017

Status: Available (was: Untriaged)
This is currently marked as failing, but sometimes passes.

The order of the "PASS" lines is inconsistent.

We should remove the expectation, and just rely on assertions here. Optionally, we should also make the order more deterministic.

Comment 5 by tdres...@chromium.org, Aug 14 2017

Mergedinto: 709028
Status: Duplicate (was: Available)
►

Sign in to add a comment