New issue
Advanced search Search tips

Issue 721983 link

Starred by 1 user
Status: Duplicate
Owner: ----
Closed: May 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 1
Type: Bug



Sign in to add a comment

"BlacklistTest.SetupFailed" is flaky (registry errors)

Project Member Reported by chromium...@appspot.gserviceaccount.com, May 13 2017 
"BlacklistTest.SetupFailed" is flaky.

This issue was created automatically by the chromium-try-flakes app. Please find the right owner to fix the respective test/step and assign this issue to them. If the step/test is infrastructure-related, please add Infra-Troopers label and change issue status to Untriaged. When done, please remove the issue from Sheriff Bug Queue by removing the Sheriff-Chromium label.

We have detected 3 recent flakes. List of all flakes can be found at https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyJAsSBUZsYWtlIhlCbGFja2xpc3RUZXN0LlNldHVwRmFpbGVkDA.

Flaky tests should be disabled within 30 minutes unless culprit CL is found and reverted. Please see more details here: https://sites.google.com/a/chromium.org/dev/developers/tree-sheriffs/sheriffing-bug-queues#triaging-auto-filed-flakiness-bugs

Comment 1 by tapted@chromium.org, May 15 2017

Labels: OS-Windows
Summary: "BlacklistTest.SetupFailed" is flaky (registry errors) (was: "BlacklistTest.SetupFailed" is flaky)
Yet more registry goop, now chrome_elf_unittests

See also  Issue 722083 ,  Issue 722017  and  Issue 722075 

[ RUN      ] BlacklistTest.SetupFailed
e:\b\c\b\win\src\base\test\test_reg_util_win.cc(106): error:       Expected: 0L
      Which is: 0
To be equal to: temp_key.Create((( HKEY ) (ULONG_PTR)((LONG)0x80000001) ), key_path.c_str(), (((0x001F0000L) | (0x0001) | (0x0002) | (0x0004) | (0x0008) | (0x0010) | (0x0020)) & (~(0x00100000L))))
      Which is: 1450
e:\b\c\b\win\src\chrome_elf\blacklist\test\blacklist_test.cc(148): error: Expected: override_manager_.OverrideRegistry((( HKEY ) (ULONG_PTR)((LONG)0x80000001) ), &temp) doesn't generate new fatal failures in the current thread.
  Actual: it does.
Backtrace:
	(No symbol) [0x00000000]
	testing::internal::TestFactoryImpl<`anonymous namespace'::BlacklistTest_SetupSucceeded_Test>::CreateTest [0x00C3321C+812]
	testing::internal::HandleExceptionsInMethodIfSupported<testing::TestCase,void> [0x00C45FAD+32]
	testing::Test::Run [0x00C4CD01+126]
	testing::TestInfo::Run [0x00C4CE61+126]
	testing::TestCase::Run [0x00C4CD8C+133]
	testing::internal::UnitTestImpl::RunAllTests [0x00C4D111+433]
	testing::internal::HandleExceptionsInMethodIfSupported<testing::internal::UnitTestImpl,bool> [0x00C45FF1+32]
	testing::UnitTest::Run [0x00C4CF35+133]
	base::TestSuite::Run [0x00CB2CAF+95]
	base::LaunchUnitTests [0x00CB0FD3+766]
	base::LaunchUnitTests [0x00CB0D22+77]
	main [0x00C3EB7F+96]
	__scrt_common_main_seh [0x00CEF16B+249] (f:\dd\vctools\crt\vcstartup\src\startup\exe_common.inl:253)
	BaseThreadInitThunk [0x75A0336A+18]
	RtlInitializeExceptionChain [0x77C89882+99]
	RtlInitializeExceptionChain [0x77C89855+54]

Comment 2 by tapted@chromium.org, May 15 2017

Mergedinto: 721245
Status: Duplicate (was: Untriaged)
►

Sign in to add a comment