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

Issue 777466 link

Starred by 2 users

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: ----



Sign in to add a comment

virtual/mojo-loading/http/tests/devtools/console-xhr-logging.js flaky

Project Member Reported by battre@chromium.org, Oct 23 2017

Issue description

Builders failed on: 
- WebKit Win7: 
  https://build.chromium.org/p/chromium.webkit/builders/WebKit%20Win7

Sample flake https://build.chromium.org/p/chromium.webkit/builders/WebKit%20Win7/builds/56826

--- e:\b\swarm_slave\w\ioesw0lv\layout-test-results\virtual/mojo-loading/http/tests/devtools/console-xhr-logging-expected.txt
+++ e:\b\swarm_slave\w\ioesw0lv\layout-test-results\virtual/mojo-loading/http/tests/devtools/console-xhr-logging-actual.txt
@@ -34,13 +34,13 @@
 requestHelper @ console-xhr-logging.js:14
 (anonymous) @ console-xhr-logging.js:21
 console-xhr-logging.js:13 sending a GET request to http://localhost:8000/devtools/resources/xhr-exists.html
-VM:37 Failed to load http://localhost:8000/devtools/resources/xhr-exists.html: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://127.0.0.1:8000' is therefore not allowed access.
+VM:37 XHR finished loading: GET "http://localhost:8000/devtools/resources/xhr-exists.html".
 makeXHR @ VM:37
 makeSimpleXHRWithPayload @ VM:13
 makeSimpleXHR @ VM:9
 requestHelper @ console-xhr-logging.js:14
 (anonymous) @ console-xhr-logging.js:22
-VM:37 XHR finished loading: GET "http://localhost:8000/devtools/resources/xhr-exists.html".
+VM:37 Failed to load http://localhost:8000/devtools/resources/xhr-exists.html: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://127.0.0.1:8000' is therefore not allowed access.
 makeXHR @ VM:37
 makeSimpleXHRWithPayload @ VM:13
 makeSimpleXHR @ VM:9

Adding a few people who may know how to route this.
 

Comment 2 by yzshen@chromium.org, Oct 23 2017

Cc: yzshen@chromium.org
Owner: ----

Removing myself from owner field. I don't think I worked on anything that is related to this. (If I have missed anything, please let me know.)

If I was assigned because of mojo-loading in the path: this is a feature using mojo URLLoader interface to replace the old IPC between browser and renderer. And I don't work on it.
Cc: -pfeldman@chromium.org
Owner: pfeldman@chromium.org
Better owner?
Project Member

Comment 4 by bugdroid1@chromium.org, Oct 24 2017

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

commit db81106a4225aac283890ba61851e843126284b7
Author: Dominic Battre <battre@chromium.org>
Date: Tue Oct 24 09:39:52 2017

virtual/mojo-loading/http/tests/devtools/console-xhr-logging.js flaky

Flakes have been observed for the test on all platforms. See bug for details.

TBR=rouslan@chromium.org, yzshen@chromium.org

Bug: 777466
Change-Id: I390da539ea0452a17dfa4cfcf86a42196babeca4
Reviewed-on: https://chromium-review.googlesource.com/733700
Commit-Queue: Dominic Battré <battre@chromium.org>
Reviewed-by: Rouslan Solomakhin <rouslan@chromium.org>
Reviewed-by: Dominic Battré <battre@chromium.org>
Cr-Commit-Position: refs/heads/master@{#511069}
[modify] https://crrev.com/db81106a4225aac283890ba61851e843126284b7/third_party/WebKit/LayoutTests/TestExpectations

Comment 5 by battre@chromium.org, Oct 24 2017

Labels: -Sheriff-Chromium
Taking this out of the sheriff queue

Comment 6 by laforge@google.com, Nov 7 2017

Components: -Internals>Network>Service Internals>Services>Network
Apologies, applied the wrong component in bulk.
Owner: caseq@chromium.org

Comment 8 by awdf@chromium.org, Apr 11 2018

Labels: Pri-1
just had this spuriously fail blocking my patch getting through the cq -  https://ci.chromium.org/buildbot/tryserver.chromium.win/win7_chromium_rel_ng/142914 (unfortunately I got 3 different unrelated failures on each automatic retry!)

Comment 9 by dxie@chromium.org, May 17 2018

Components: -Internals>Services>Network Blink>Loader
this is running without the network service. Giving it to blink loading for further triage.
Cc: jarhar@chromium.org
Components: -Blink>Loader Tests>Flaky Platform>DevTools>Network
Owner: l...@chromium.org

Sign in to add a comment