MultiprocessMessagePipeTestWithPeerSupport.MessagePipeTwoPassing flaked on mojo_system_unittests on Fuchsia |
||
Issue descriptionhttps://build.chromium.org/p/chromium.fyi/builders/Fuchsia/builds/8646 [00041.055] 02426.02614> [ RUN ] MultiprocessMessagePipeTestWithPeerSupport.MessagePipeTwoPassing/1 [00041.055] 02426.02614> [3:1215306544:0811/061009.868322:20800671:WARNING:test_suite.cc(235)] Test launcher output path /tmp/.org.chromium.Chromium.jdJGKb/test_results.xml exists. Not adding test launcher result printer. [00041.055] 02426.02614> ../../mojo/edk/system/multiprocess_message_pipe_unittest.cc:605: Failure [00041.055] 02426.02614> Expected: MOJO_RESULT_OK [00041.055] 02426.02614> Which is: 0 [00041.055] 02426.02614> To be equal to: WaitForSignals(mp1, MOJO_HANDLE_SIGNAL_READABLE, &hss) [00041.055] 02426.02614> Which is: 9 [00041.055] 02426.02614> [ FAILED ] MultiprocessMessagePipeTestWithPeerSupport.MessagePipeTwoPassing/1, where GetParam() = 4-byte object <01-00 00-00> (390 ms)
,
Aug 11 2017
,
Aug 16 2017
,
Sep 1 2017
These were MOJO_RESULT_FAILED_PRECONDITION, which matches the result codes from issue 754770 , curiously, possibly also indicating that the peer was closing the pipe unexpectedly. No more sign of these lately, though, so closing out for now. |
||
►
Sign in to add a comment |
||
Comment 1 by scottmg@chromium.org
, Aug 11 2017