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

Issue 765791 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Oct 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

FindInPageControllerTest.FindLongString failing on chromium.win/Win7 Tests (dbg)(1)

Project Member Reported by kelv...@chromium.org, Sep 15 2017

Issue description

browser_tests failing on chromium.win/Win7 Tests (dbg)(1)

Builders failed on: 
- Win7 Tests (dbg)(1): 
  https://build.chromium.org/p/chromium.win/builders/Win7%20Tests%20%28dbg%29%281%29

Failure Link:
https://luci-logdog.appspot.com/v/?s=chromium%2Fbb%2Fchromium.win%2FWin7_Tests__dbg__1_%2F63246%2F%2B%2Frecipes%2Fsteps%2Fbrowser_tests%2F0%2Flogs%2FFindInPageControllerTest.FindLongString%2F0


Log:
[ RUN      ] FindInPageControllerTest.FindLongString
[4932:5484:0915/100305.094:ERROR:direct_composition_surface_win.cc(1095)] Failing to detect HDR, couldn't retrieve D3D11 device from ANGLE.
[4932:5484:0915/100305.247:INFO:media_foundation_video_encode_accelerator_win.cc(335)] Windows versions earlier than 8 are not supported.
Assertion failed: false, file ../../third_party/swiftshader/src/OpenGL/libEGL/Surface.cpp, line 281
[ RUN      ] FindInPageControllerTest.FindLongString
[2584:4320:0915/101527.522:ERROR:direct_composition_surface_win.cc(1095)] Failing to detect HDR, couldn't retrieve D3D11 device from ANGLE.
[2584:4320:0915/101527.609:INFO:media_foundation_video_encode_accelerator_win.cc(335)] Windows versions earlier than 8 are not supported.
[ RUN      ] FindInPageControllerTest.FindLongString
[3684:3660:0915/101701.994:ERROR:direct_composition_surface_win.cc(1095)] Failing to detect HDR, couldn't retrieve D3D11 device from ANGLE.
[3684:3660:0915/101702.038:INFO:media_foundation_video_encode_accelerator_win.cc(335)] Windows versions earlier than 8 are not supported.
[ RUN      ] FindInPageControllerTest.FindLongString
[6112:4272:0915/101747.848:ERROR:direct_composition_surface_win.cc(1095)] Failing to detect HDR, couldn't retrieve D3D11 device from ANGLE.
[6112:4272:0915/101747.893:INFO:media_foundation_video_encode_accelerator_win.cc(335)] Windows versions earlier than 8 are not supported.
Assertion failed: false, file ../../third_party/swiftshader/src/OpenGL/libEGL/Surface.cpp, line 281


 
Labels: Pri-2 Type-Bug
Marking P2 as the test has only failed once.
Labels: -Sheriff-Chromium OS-Windows
Owner: msw@chromium.org
Status: Assigned (was: Available)
Hi msw@, could you redirect or close?

Comment 4 by msw@chromium.org, Sep 20 2017

Cc: stanisc@chromium.org sugoi@google.com jbau...@chromium.org nicolasc...@google.com
Components: Internals>GPU
Owner: hubbe@chromium.org
Why assign this to me? Use git blame for assignments when there's a clear error and assertion.
Assigning to hubbe@ for the direct_composition_surface_win.cc error
CC'ing jbauman@ as reviewer and stanisc@ as windows gpu/ipc/service owner.
CC'ing swiftshader owners for that assertion failure.

Comment 5 by hubbe@chromium.org, Sep 20 2017

Cc: -sugoi@google.com hubbe@chromium.org
Owner: sugoi@chromium.org
The HDR message is just a warning, and shouldn't have an impact on the test. (Except for being annoying.)

Passing the buck down the line.

Comment 6 by sugoi@chromium.org, Oct 3 2017

The SwiftShader assertion was removed here:
https://swiftshader-review.googlesource.com/#/c/SwiftShader/+/12808/

We'll see if this affects this test's result on the Win7 Tests (dbg) bot in the next DEPS roll.
Project Member

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

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

commit 5955bc576d147925fb8966ca7b91a23f7c91591e
Author: Alexis Hetu <sugoi@google.com>
Date: Wed Oct 04 01:03:13 2017

Roll SwiftShader bc6ce4f..9d56da2

https://swiftshader.googlesource.com/SwiftShader.git/+log/bc6ce4f..9d56da2

BUG= chromium:763382 , chromium:763384 , chromium:763435 , chromium:765094 , chromium:765791 , chromium:765939 

TBR=kbr@chromium.org

TEST=bots

CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.win:win_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel,linux_chromium_cfi_rel_ng;master.tryserver.chromium.android:android_optional_gpu_tests_rel

Change-Id: Idd52bdc26eba54615838baf5dc65705a8a4be631
Reviewed-on: https://chromium-review.googlesource.com/699156
Commit-Queue: Alexis Hétu <sugoi@chromium.org>
Reviewed-by: Alexis Hétu <sugoi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506259}
[modify] https://crrev.com/5955bc576d147925fb8966ca7b91a23f7c91591e/DEPS

Comment 8 by sugoi@chromium.org, Oct 4 2017

Status: Fixed (was: Assigned)
Marking as fixed. Please reopen if this issue reappears. Thanks.

Sign in to add a comment