Issue metadata
Sign in to add a comment
|
"CrExtensionsA11yTestWithMultipleExensions.WithExtensions_duplicate_id" is flaky |
||||||||||||||||||||||||
Issue description"CrExtensionsA11yTestWithMultipleExensions.WithExtensions_duplicate_id" 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=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyUAsSBUZsYWtlIkVDckV4dGVuc2lvbnNBMTF5VGVzdFdpdGhNdWx0aXBsZUV4ZW5zaW9ucy5XaXRoRXh0ZW5zaW9uc19kdXBsaWNhdGVfaWQM. 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
,
Dec 28 2017
This looks like V8 issue. Call stack is similar on Linux and Windows. [10316:10316:1222/112951.394115:INFO:CONSOLE(1225)] "Running TestCase CrExtensionsA11yTestWithMultipleExensions.WithExtensions_duplicate_id", source: test_api.js (1225) # # Fatal error in ../../v8/src/compiler/scheduler.cc, line 1411 # Debug check failed: min_block == BasicBlock::GetCommonDominator(block, min_block) (0x27ab0544afb0 vs. 0x27ab0544c498). # #0 0x00000540de4c base::debug::StackTrace::StackTrace() #1 0x000008ab7abb gin::(anonymous namespace)::PrintStackTrace() #2 0x00000893853c V8_Fatal() #3 0x000008938305 v8::base::(anonymous namespace)::DefaultDcheckHandler() #4 0x000004a5e029 v8::internal::compiler::ScheduleLateNodeVisitor::VisitNode() #5 0x000004a5da6a v8::internal::compiler::ScheduleLateNodeVisitor::ProcessQueue() #6 0x000004a5796b v8::internal::compiler::Scheduler::ScheduleLate() #7 0x000004a56dea v8::internal::compiler::Scheduler::ComputeSchedule() #8 0x000004a33468 v8::internal::compiler::EffectControlLinearizationPhase::Run() #9 0x000004a290f0 v8::internal::compiler::PipelineImpl::OptimizeGraph() #10 0x000004a28c50 v8::internal::compiler::PipelineCompilationJob::ExecuteJobImpl() #11 0x0000048d3176 v8::internal::CompilationJob::ExecuteJob() #12 0x0000048d1691 v8::internal::OptimizingCompileDispatcher::CompileNext() #13 0x0000048d24d9 v8::internal::OptimizingCompileDispatcher::CompileTask::RunInternal() #14 0x00000540f44a base::debug::TaskAnnotator::RunTask() #15 0x00000548ecd8 base::internal::TaskTracker::RunOrSkipTask() #16 0x00000548f8eb base::internal::TaskTrackerPosix::RunOrSkipTask() #17 0x00000548deaa base::internal::TaskTracker::RunNextTask() #18 0x00000548b146 base::internal::SchedulerWorker::Thread::ThreadMain() #19 0x000005497aff base::(anonymous namespace)::ThreadFunc() #20 0x7f4c62c53184 start_thread #21 0x7f4c5d0adffd clone
,
Jan 2 2018
Jaro, any clue what is going on here?
,
Jan 2 2018
Looks like duplicate of https://crbug.com/797130 , which was already fixed. Does it still flake?
,
Jan 8 2018
,
Feb 21 2018
Marked as "Fixed" instead to mitigate the bug 813223 in chromium-try-flakes. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by chromium...@appspot.gserviceaccount.com
, Dec 27 2017