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

Issue 652567 link

Starred by 1 user
Status: Fixed
Owner:
█ jialiul@chromium.org
Last visit > 30 days ago
Closed: Oct 2016
Cc:
horo@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug-Regression



Sign in to add a comment

browser_tests (SafeBrowsingBlockingPageBrowserTestWithThreatTypeAndIsolationSetting) on Windows-10-10586 failing on chromium.win/Win10 Tests x64

Project Member Reported by horo@chromium.org, Oct 4 2016 
browser_tests on Windows-10-10586 failing on chromium.win/Win10 Tests x64

Type: build-failure

Builders failed on: 
- Win10 Tests x64: 
  https://build.chromium.org/p/chromium.win/builders/Win10%20Tests%20x64


https://uberchromegw.corp.google.com/i/chromium.win/builders/Win10%20Tests%20x64/builds/4845/steps/browser_tests%20on%20Windows-10-10586/logs/SafeBrowsingBlockingPageBrowserTestWithThreatTypeAndIsolationSetting_SafeBrowsingBlockingPageBrowserTest.IframeOptInAndReportThreatDetails_2

SafeBrowsingBlockingPageBrowserTestWithThreatTypeAndIsolationSetting/SafeBrowsingBlockingPageBrowserTest.IframeOptInAndReportThreatDetails/2 (run #1):
[ RUN      ] SafeBrowsingBlockingPageBrowserTestWithThreatTypeAndIsolationSetting/SafeBrowsingBlockingPageBrowserTest.IframeOptInAndReportThreatDetails/2
[8992:1716:1003/211827:WARNING:chrome_browser_main_win.cc(419)] Command line too long for RegisterApplicationRestart
[2068:7476:1003/211827:ERROR:mf_helpers.cc(12)] Error in dxva_video_decode_accelerator_win.cc on line 297
[8992:6564:1003/211828:ERROR:test_database_manager.cc(58)] NOT IMPLEMENTED
[8992:6564:1003/211828:ERROR:test_database_manager.cc(58)] NOT IMPLEMENTED
[2068:7476:1003/211828:ERROR:gles2_cmd_decoder.cc(16313)] [.DisplayCompositor-0000022BF555B9B0]GL ERROR :GL_INVALID_OPERATION : glCreateAndConsumeTextureCHROMIUM: invalid mailbox name
[2068:7476:1003/211828:ERROR:gles2_cmd_decoder.cc(9027)] [.DisplayCompositor-0000022BF555B9B0]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[2068:7476:1003/211828:ERROR:gles2_cmd_decoder.cc(16313)] [.DisplayCompositor-0000022BF555B9B0]GL ERROR :GL_INVALID_OPERATION : glCreateAndConsumeTextureCHROMIUM: invalid mailbox name
[2068:7476:1003/211828:ERROR:gles2_cmd_decoder.cc(9027)] [.DisplayCompositor-0000022BF555B9B0]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
Backtrace:
	base::internal::BindState<void (__cdecl content::FrameWatcher::*)(cc::CompositorFrameMetadata) __ptr64,scoped_refptr<content::FrameWatcher>,base::internal::PassedWrapper<cc::CompositorFrameMetadata> >::Destroy [0x00007FF6C444386F+79]
	content::WebContentsImpl::AttachInterstitialPage [0x00007FF6C3A8C432+94]
	content::InterstitialPageImpl::DidNavigate [0x00007FF6C388E1DC+140]
	content::RenderFrameHostImpl::OnDidCommitProvisionalLoad [0x00007FF6C38A8738+1480]
	content::RenderFrameHostImpl::OnMessageReceived [0x00007FF6C38A9093+919]
	content::RenderProcessHostImpl::OnMessageReceived [0x00007FF6C39D2B57+883]
	IPC::ChannelProxy::Context::OnDispatchMessage [0x00007FF6C4D300F8+40]
	base::debug::TaskAnnotator::RunTask [0x00007FF6C3FE11F7+343]
	base::MessageLoop::RunTask [0x00007FF6C3F75BD9+873]
	base::MessageLoop::DoWork [0x00007FF6C3F751FA+394]
	base::MessagePumpForUI::DoRunLoop [0x00007FF6C3FE2381+113]
	base::MessagePumpWin::Run [0x00007FF6C3FE2FB4+84]
	base::RunLoop::Run [0x00007FF6C3F783BE+46]
	content::RunThisRunLoop [0x00007FF6C443F79E+86]
	content::MessageLoopRunner::Run [0x00007FF6C443F484+28]
	content::RunTaskAndWaitForInterstitialDetach [0x00007FF6C44451F3+227]
	content::WaitForInterstitialDetach [0x00007FF6C444680E+34]
	safe_browsing::SafeBrowsingBlockingPageBrowserTest_IframeOptInAndReportThreatDetails_Test::RunTestOnMainThread [0x00007FF6C2BD4251+1109]
	InProcessBrowserTest::RunTestOnMainThreadLoop [0x00007FF6C4008E4E+238]
	content::BrowserTestBase::ProxyRunTestOnMainThreadLoop [0x00007FF6C44488DA+298]
	ChromeBrowserMainParts::PreMainMessageLoopRunImpl [0x00007FF6C42B980E+3778]
	ChromeBrowserMainParts::PreMainMessageLoopRun [0x00007FF6C42B88D8+204]
	content::BrowserMainLoop::PreMainMessageLoopRun [0x00007FF6C37EA51F+155]
	content::StartupTaskRunner::RunAllTasksNow [0x00007FF6C3A683B8+56]
	content::BrowserMainLoop::CreateStartupTasks [0x00007FF6C37E8014+484]
	content::BrowserMainRunnerImpl::Initialize [0x00007FF6C37EBD6F+771]
	content::BrowserMain [0x00007FF6C37E68E5+153]
	content::RunNamedProcessTypeMain [0x00007FF6C3F52BA2+178]
	content::ContentMainRunnerImpl::Run [0x00007FF6C3F52A97+203]
	content::ContentMain [0x00007FF6C3F51E40+48]
	content::BrowserTestBase::SetUp [0x00007FF6C44491FC+1608]
	InProcessBrowserTest::SetUp [0x00007FF6C40093BE+322]
	testing::internal::HandleExceptionsInMethodIfSupported<testing::Test,void> [0x00007FF6C48C2EBD+61]
	testing::Test::Run [0x00007FF6C48CDE92+74]
	testing::TestInfo::Run [0x00007FF6C48CE0B1+161]
	testing::TestCase::Run [0x00007FF6C48CDF99+165]
	testing::internal::UnitTestImpl::RunAllTests [0x00007FF6C48CE456+562]
	testing::internal::HandleExceptionsInMethodIfSupported<testing::internal::UnitTestImpl,bool> [0x00007FF6C48C2F5D+61]
	testing::UnitTest::Run [0x00007FF6C48CE1F1+217]
	base::TestSuite::Run [0x00007FF6C40150B5+137]
	ChromeTestSuiteRunner::RunTestSuite [0x00007FF6C6C2C741+45]
	content::LaunchTests [0x00007FF6C4440CB7+611]
	main [0x00007FF6C6C2C36F+83]
	__scrt_common_main_seh [0x00007FF6C6BE8679+285] (f:\ddctools\crtcstartup\src\startup\exe_common.inl:253)
	BaseThreadInitThunk [0x00007FF8C7BD8102+34]
	RtlUserThreadStart [0x00007FF8C7E3C574+52]

Comment 1 by jialiul@chromium.org, Oct 4 2016

Cc: horo@chromium.org
er..... I cannot figure out which CL on the blame list caused this failure. Next build #4846 seems green again. horo@, Does it mean flakiness?

Comment 2 by horo@chromium.org, Oct 4 2016 

I think it is flaky.
This test failed also in the build 4777.
https://build.chromium.org/p/chromium.win/builders/Win10%20Tests%20x64/builds/4777/steps/browser_tests%20on%20Windows-10-10586/logs/stdio

jialiul@ do you have any idea about this failure?

Comment 3 by jialiul@chromium.org, Oct 4 2016 

No, I have no idea. I don't think there is recent change on relevant files. I'll dig more tomorrow. If flakiness only happens on Win, I can disable this test on Win.

Comment 4 by horo@chromium.org, Oct 4 2016

Labels: Sheriff-Chromium

Comment 5 by jialiul@chromium.org, Oct 4 2016 

horo@, do you know how can I search for all the failure for this test case across different builds? I want to check if only IframeOptInAndReportThreatDetails/2 fails or it fails on all the parameter combination.

Comment 7 by horo@chromium.org, Oct 5 2016

Labels: -Sheriff-Chromium
Status: Assigned (was: Available)
Project Member

Comment 8 by bugdroid1@chromium.org, Oct 7 2016 

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

commit f789d6d04bc5de7c37a7799a0cb843c5e687b385
Author: jialiul <jialiul@chromium.org>
Date: Fri Oct 07 22:16:19 2016

Simplify SafeBrowsingBlockingPageBrowserTest.IframeOptInAndReportThreatDetails
test cases to reduce flakiness.
Also corrected some constant names (malware->malicious), since tests are not
limited to malware threat type.

BUG= 652567 

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

[modify] https://crrev.com/f789d6d04bc5de7c37a7799a0cb843c5e687b385/chrome/browser/safe_browsing/safe_browsing_blocking_page_test.cc
[modify] https://crrev.com/f789d6d04bc5de7c37a7799a0cb843c5e687b385/chrome/test/data/safe_browsing/malware2.html

Comment 9 by jialiul@chromium.org, Oct 7 2016

Status: Fixed (was: Assigned)
►

Sign in to add a comment