I was using base_unittests as a test for working on run scripts when this test failed.
[ RUN ] MessageLoopTaskRunnerTest.PostTaskAndReply_DeadReplyTaskRunnerBehavior
../../base/message_loop/message_loop_task_runner_unittest.cc:247: Failure
Value of: reply_deleted_on
Actual: true
Expected: false
Stack trace:
#00: StackTraceGetter::CurrentStackTrace(int, int) at third_party/googletest/custom/gtest/internal/custom/stack_trace_getter.cc:24
#01: testing::internal::UnitTestImpl::CurrentOsStackTraceExceptTop(int) at third_party/googletest/src/googletest/src/gtest.cc:846
#02: testing::internal::AssertHelper::operator=(testing::Message const&) const at third_party/googletest/src/googletest/src/gtest.cc:418
#03: base::MessageLoopTaskRunnerTest_PostTaskAndReply_DeadReplyTaskRunnerBehavior_Test::TestBody() at base/message_loop/message_loop_task_runner_unittest.cc:247
#04: void testing::internal::InvokeHelper<void, std::__2::tuple<> >::InvokeMethod<base::RunLoop, void (base::RunLoop::*)()>(base::RunLoop*, void (base::RunLoop::*)(), std::__2::tuple<> const&) at third_party/googletest/src/googlemock/include/gmock/gmock-generated-actions.h:68
...
[3384/3386] MessageLoopForIOOnMainThread/FileDescriptorWatcherTest.DeleteControllerAfterDeleteMessageLoopForIO/0 (100 ms)
[3385/3386] MessageLoopForIOOnOtherThread/FileDescriptorWatcherTest.WatchWritable/0 (0 ms)
[3386/3386] MessageLoopForIOOnOtherThread/FileDescriptorWatcherTest.WatchReadableOneByte/0 (201 ms)
1 test failed:
MessageLoopTaskRunnerTest.PostTaskAndReply_DeadReplyTaskRunnerBehavior (../../base/message_loop/message_loop_task_runner_unittest.cc:204)
Tests took 30 seconds.
Haven't tried to --gtest_repeat it to see if I can get it to fail regularly.
Comment 1 by scottmg@chromium.org
, Sep 26Status: Duplicate (was: Available)