SecurityKeyIpcServerTest.InitialIpcConnectionTimeout_ConnectOnly flaky in remoting_unittests |
||
Issue descriptionFiled by sheriff-o-matic@appspot.gserviceaccount.com on behalf of olka@google.com Dashboard: https://test-results.appspot.com/dashboards/flakiness_dashboard.html#testType=remoting_unittests&tests=SecurityKeyIpcServerTest.InitialIpcConnectionTimeout_ConnectOnly Example failure: https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/Mac%20ASan%2064%20Tests%20%281%29/44875 Log: [ RUN ] SecurityKeyIpcServerTest.InitialIpcConnectionTimeout_ConnectOnly ../../remoting/host/security_key/security_key_ipc_server_unittest.cc:325: Failure The difference between elapsed_time.InMilliseconds() and kInitialConnectTimeoutMs is 135, which exceeds kConnectionTimeoutErrorDeltaMs, where elapsed_time.InMilliseconds() evaluates to 385, kInitialConnectTimeoutMs evaluates to 250, and kConnectionTimeoutErrorDeltaMs evaluates to 100. Stack trace: 0 remoting_unittests 0x0000000106e85272 testing::internal::UnitTestImpl::CurrentOsStackTraceExceptTop(int) + 242 1 remoting_unittests 0x0000000106e83e77 testing::internal::AssertHelper::operator=(testing::Message const&) const + 359 2 remoting_unittests 0x000000010b7ee651 remoting::SecurityKeyIpcServerTest_InitialIpcConnectionTimeout_ConnectOnly_Test::TestBody() + 1633 [ FAILED ] SecurityKeyIpcServerTest.InitialIpcConnectionTimeout_ConnectOnly (407 ms) [ RUN ] SecurityKeyIpcServerTest.InitialIpcConnectionTimeout_ConnectOnly ../../remoting/host/security_key/security_key_ipc_server_unittest.cc:325: Failure The difference between elapsed_time.InMilliseconds() and kInitialConnectTimeoutMs is 136, which exceeds kConnectionTimeoutErrorDeltaMs, where elapsed_time.InMilliseconds() evaluates to 386, kInitialConnectTimeoutMs evaluates to 250, and kConnectionTimeoutErrorDeltaMs evaluates to 100. Stack trace: 0 remoting_unittests 0x0000000105db4272 testing::internal::UnitTestImpl::CurrentOsStackTraceExceptTop(int) + 242 1 remoting_unittests 0x0000000105db2e77 testing::internal::AssertHelper::operator=(testing::Message const&) const + 359 2 remoting_unittests 0x000000010a71d651 remoting::SecurityKeyIpcServerTest_InitialIpcConnectionTimeout_ConnectOnly_Test::TestBody() + 1633 [ FAILED ] SecurityKeyIpcServerTest.InitialIpcConnectionTimeout_ConnectOnly (409 ms) [ RUN ] SecurityKeyIpcServerTest.InitialIpcConnectionTimeout_ConnectOnly ../../remoting/host/security_key/security_key_ipc_server_unittest.cc:325: Failure The difference between elapsed_time.InMilliseconds() and kInitialConnectTimeoutMs is 135, which exceeds kConnectionTimeoutErrorDeltaMs, where elapsed_time.InMilliseconds() evaluates to 385, kInitialConnectTimeoutMs evaluates to 250, and kConnectionTimeoutErrorDeltaMs evaluates to 100. Stack trace: 0 remoting_unittests 0x000000010f710272 testing::internal::UnitTestImpl::CurrentOsStackTraceExceptTop(int) + 242 1 remoting_unittests 0x000000010f70ee77 testing::internal::AssertHelper::operator=(testing::Message const&) const + 359 2 remoting_unittests 0x0000000114079651 remoting::SecurityKeyIpcServerTest_InitialIpcConnectionTimeout_ConnectOnly_Test::TestBody() + 1633 [ FAILED ] SecurityKeyIpcServerTest.InitialIpcConnectionTimeout_ConnectOnly (407 ms) [ RUN ] SecurityKeyIpcServerTest.InitialIpcConnectionTimeout_ConnectOnly ../../remoting/host/security_key/security_key_ipc_server_unittest.cc:325: Failure The difference between elapsed_time.InMilliseconds() and kInitialConnectTimeoutMs is 131, which exceeds kConnectionTimeoutErrorDeltaMs, where elapsed_time.InMilliseconds() evaluates to 381, kInitialConnectTimeoutMs evaluates to 250, and kConnectionTimeoutErrorDeltaMs evaluates to 100. Stack trace: 0 remoting_unittests 0x0000000104718272 testing::internal::UnitTestImpl::CurrentOsStackTraceExceptTop(int) + 242 1 remoting_unittests 0x0000000104716e77 testing::internal::AssertHelper::operator=(testing::Message const&) const + 359 2 remoting_unittests 0x0000000109081651 remoting::SecurityKeyIpcServerTest_InitialIpcConnectionTimeout_ConnectOnly_Test::TestBody() + 1633 [ FAILED ] SecurityKeyIpcServerTest.InitialIpcConnectionTimeout_ConnectOnly (403 ms)
,
Oct 9
Actually, most of the suite is flaky on Mac. Holding off on disabling. Jamie: Is this as simple as increasing kInitialConnectTimeoutMs? https://test-results.appspot.com/dashboards/flakiness_dashboard.html#testType=remoting_unittests&tests=SecurityKeyIpcServerTest.*
,
Oct 10
|
||
►
Sign in to add a comment |
||
Comment 1 by waff...@chromium.org
, Oct 9Labels: OS-Mac
Owner: jamiewa...@chromium.org