"PipelineIntegrationTest.TrackStatusChangesWhileSuspended" is flaky |
|||||
Issue description"PipelineIntegrationTest.TrackStatusChangesWhileSuspended" 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 5 recent flakes. List of all flakes can be found at https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyQwsSBUZsYWtlIjhQaXBlbGluZUludGVncmF0aW9uVGVzdC5UcmFja1N0YXR1c0NoYW5nZXNXaGlsZVN1c3BlbmRlZAw. 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
,
Sep 6 2016
,
Sep 6 2016
,
Sep 6 2016
,
Oct 17 2016
I've investigated this and flakiness was due to the issue tracked by crbug.com/638018. It has since been fixed and I've re-landed the CL that added the TrackStatusChangesWhileSuspended test as https://codereview.chromium.org/2378893002/. Please re-open if you still see flakiness. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by magjed@chromium.org
, Sep 5 2016This test is hitting this DCHECK: void FFmpegDemuxerStream::FlushBuffers() { ... DCHECK(read_cb_.is_null()) << "There should be no pending read"; Log: [ RUN ] PipelineIntegrationTest.TrackStatusChangesWhileSuspended [31817:31817:0902/111635:18030513095:FATAL:ffmpeg_demuxer.cc(587)] Check failed: read_cb_.is_null(). There should be no pending read #0 0x000000e3160e base::debug::StackTrace::StackTrace() #1 0x000000e3adda logging::LogMessage::~LogMessage() #2 0x000000a7ee9b media::FFmpegDemuxerStream::FlushBuffers() #3 0x000000a815ae media::FFmpegDemuxer::OnSeekFrameDone() #4 0x000000a8651a base::internal::ReplyAdapter<>() #5 0x000000e6109b base::(anonymous namespace)::PostTaskAndReplyRelay::RunReplyAndSelfDestruct() #6 0x000000e862c6 base::debug::TaskAnnotator::RunTask() #7 0x000000e3f6f5 base::MessageLoop::RunTask() #8 0x000000e3fa18 base::MessageLoop::DeferOrRunPendingTask() #9 0x000000e3fd5b base::MessageLoop::DoWork() #10 0x000000e412ec base::MessagePumpDefault::Run() #11 0x000000e3f23d base::MessageLoop::RunHandler() #12 0x000000e4f8a0 base::RunLoop::Run() #13 0x0000009eece9 media::PipelineIntegrationTestBase::Resume() #14 0x00000091e408 media::PipelineIntegrationTest_TrackStatusChangesWhileSuspended_Test::TestBody() #15 0x000000e06b27 testing::Test::Run() #16 0x000000e07703 testing::TestInfo::Run() #17 0x000000e07b97 testing::TestCase::Run() #18 0x000000e0ebd7 testing::internal::UnitTestImpl::RunAllTests() #19 0x000000e0e82a testing::UnitTest::Run() #20 0x000000ab7963 base::TestSuite::Run() #21 0x000000ab8b04 base::LaunchUnitTests() #22 0x0000008ab3c3 main #23 0x7fa0e044c7ed __libc_start_main #24 0x00000048fd21 <unknown> DaleCurtis@ - Please help triage this issue to someone suitable.