1379365 - Intermittent TestNrSocketTest.PrivateToPublicConnectivityTcp | Value of: CheckTcpConnectivity(private_addrs_[0], public_addrs_[0])

Status: RESOLVED INCOMPLETE

(Core :: WebRTC: Networking, defect, P2)

Description

[Treeherder Bug Filer]

Filed by: philringnalda [at] gmail.com

https://treeherder.mozilla.org/logviewer.html#?job_id=112722998&repo=autoland

https://queue.taskcluster.net/v1/task/M-eNT1jFSsG6E-jSWGPQ5A/runs/0/artifacts/public/logs/live_backing.log

Comment 1

[Intermittent Failures Robot]

1 failures in 656 pushes (0.002 failures/push) were associated with this bug in the last 7 days.   

Repository breakdown:
* autoland: 1

Platform breakdown:
* linux64: 1

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1379365&startday=2017-07-03&endday=2017-07-09&tree=all

Comment 2

[Jan-Ivar Bruaroey [:jib] (needinfo? me)]

The crash seems to be in RingbufferDumper::DumpRingBuffer_s ... called from MOZ_ReportAssertionFailure

This looks like broken debug output.

High P2, it may be valuable to fix the debug output to not crash, so we can learn more about failures of this type, and not have them show up as crashes.

Comment 3

[Nils Ohlmeier [:drno]]

My guess is that RingbufferDumper::OnTestPartResult()
http://searchfox.org/mozilla-central/rev/5dadcbe55b4ddd1e448c06c77390ff6483aa009b/media/mtransport/test/gtest_ringbuffer_dumper.h#65
and RingbufferDumper::OnTestEnd() could race and the ring buffer could get destroyed before getting dumped.

If that's whats going on here it only affects our gtest.

We probably need ref-count when doing the WrapRunnable calls in RingbufferDumper.

Comment 4

[Intermittent Failures Robot]

1 failures in 888 pushes (0.001 failures/push) were associated with this bug in the last 7 days.   

Repository breakdown:
* mozilla-inbound: 1

Platform breakdown:
* osx-10-10: 1

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1379365&startday=2017-07-31&endday=2017-08-06&tree=all