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

Issue 671477 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Last visit > 30 days ago
Closed: Jan 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 3
Type: Bug
Proj-Servicification

Blocking:
issue 601332
issue 669357



Sign in to add a comment

virtual/mojo-loading/http/tests/inspector/debugger/fetch-breakpoints.html is flaky when run in random order on Windows

Project Member Reported by jeffcarp@chromium.org, Dec 6 2016

Issue description

virtual/mojo-loading/http/tests/inspector/debugger/fetch-breakpoints.html

appears to be flaky when run in random order. Example failing builds:

https://luci-milo.appspot.com/buildbot/chromium.fyi/WebKit%20Win%20-%20RandomOrder/245
https://luci-milo.appspot.com/buildbot/chromium.fyi/WebKit%20Win%20-%20RandomOrder/301
https://luci-milo.appspot.com/buildbot/chromium.fyi/WebKit%20Win%20-%20RandomOrder/308
https://luci-milo.appspot.com/buildbot/chromium.fyi/WebKit%20Win%20-%20RandomOrder/312
https://luci-milo.appspot.com/buildbot/chromium.fyi/WebKit%20Win%20-%20RandomOrder/313

Steps to reproduce:

This should pass consistently:
Tools/Scripts/run-layout-tests virtual/mojo-loading/http/tests/inspector/debugger/

This should fail intermittently:
Tools/Scripts/run-layout-tests virtual/mojo-loading/http/tests/inspector/debugger/ --order=random

We're working on removing order dependency from Blink layout tests. More context here:
https://docs.google.com/document/d/11-628Ny6hY__kfIv__zVD0m3rA0OB9tQLLC_gJI_PNg/edit

 
Labels: OS-Windows
Description: Show this description
Owner: kozyatinskiy@chromium.org
Status: Assigned (was: Untriaged)
Cc: yhirano@chromium.org
Looking at the last few "WebKit Win - RandomOrder" runs, it seems fixed somehow. jeffcarp@, what do you think?
Blocking: 669357
Status: WontFix (was: Assigned)
I'll close it since it's not reproducible now, feel free to reopen it if it happens again.
Project Member

Comment 8 by bugdroid1@chromium.org, Jan 30 2017

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

commit 1e8b5cfd4f7a74990a9b3bb7e0a0f095ca91ef3b
Author: yhirano <yhirano@chromium.org>
Date: Mon Jan 30 22:46:18 2017

virtual/mojo-loading/http/tests/inspector/debugger/fetch-breakpoints.html is no longer flaky

TBR=kozyatinskiy@chromium.org
BUG= 671477 

Review-Url: https://codereview.chromium.org/2662983002
Cr-Commit-Position: refs/heads/master@{#447094}

[modify] https://crrev.com/1e8b5cfd4f7a74990a9b3bb7e0a0f095ca91ef3b/third_party/WebKit/LayoutTests/TestExpectations

Oops I'm sorry I missed the earlier message! The test is still ignored in TestExpectations:
https://cs.chromium.org/chromium/src/third_party/WebKit/LayoutTests/TestExpectations?q=virtual/mojo-loading/http/tests/inspector/debugger/fetch-breakpoints.html&sq=package:chromium&dr=C&l=2224

I can assign this to myself, remove it from TestExpectations, and see if it fails in ongoing builds. Does that sound like a reasonable plan going forward?
Just saw the CL, thanks
Components: Internals>Network>Service
Components: -Internals>Network>Service Internals>Services>Network
Apologies, applied the wrong component in bulk.

Sign in to add a comment