HostPortPairTest.HostForURL flaky in net_unittests on ios-simulator |
||||||
Issue descriptionFailure seen here: https://ci.chromium.org/buildbot/tryserver.chromium.mac/ios-simulator/352703 Log excerpt: [----------] 7 tests from HostPortPairTest [ RUN ] HostPortPairTest.Parsing [ OK ] HostPortPairTest.Parsing (0 ms) [ RUN ] HostPortPairTest.BadString [ OK ] HostPortPairTest.BadString (0 ms) [ RUN ] HostPortPairTest.Emptiness [ OK ] HostPortPairTest.Emptiness (0 ms) [ RUN ] HostPortPairTest.ToString [ OK ] HostPortPairTest.ToString (0 ms) [ RUN ] HostPortPairTest.HostForURL [14374:771:1201/160032.747066:10851513072768:FATAL:host_port_pair.cc(68)] Host has a null char: a%00.%00com 0 net_unittests 0x000000010c4441bd base::debug::StackTrace::StackTrace(unsigned long) + 157 1 net_unittests 0x000000010c4441fd base::debug::StackTrace::StackTrace(unsigned long) + 29 2 net_unittests 0x000000010c44266c base::debug::StackTrace::StackTrace() + 28 3 net_unittests 0x000000010c4ac73f logging::LogMessage::~LogMessage() + 479 4 net_unittests 0x000000010c4aa0e5 logging::LogMessage::~LogMessage() + 21 5 net_unittests 0x000000010b678c4f net::HostPortPair::HostForURL() const + 351 6 net_unittests 0x00000001089c19a3 net::(anonymous namespace)::HostPortPairTest_HostForURL_Test::TestBody() + 1587 7 net_unittests 0x000000010b65935e void testing::internal::HandleSehExceptionsInMethodIfSupported<testing::Test, void>(testing::Test*, void (testing::Test::*)(), char const*) + 126 These tests must be reliable. I see that a bug about net_unittests is open in Issue 641708 with no action for months! Will someone please investigate this?
,
Dec 2 2017
,
Dec 2 2017
ah, it looks like this is hanging on EXPECT_DFATAL on iOS - I inadvertantly thought the FATAL I was seeing on MBP was the issue, but it's the expected behavior. The hang still needs to be addressed but wondering if it's how EXPECT_DFATAL handled in iOS test harness.
,
Dec 6 2017
,
Aug 17
,
Aug 20
Not sure if this test is still failing. Can someone check?
,
Aug 20
|
||||||
►
Sign in to add a comment |
||||||
Comment 1 by cbentzel@chromium.org
, Dec 2 2017