If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Intermittent WebRtcIceConnectTest.TestConnectTcp | Value of: res

NEW
Unassigned

Status

()

Core
WebRTC
P5
normal
Rank:
25
6 months ago
7 days ago

People

(Reporter: Treeherder Bug Filer, Unassigned)

Tracking

({intermittent-failure})

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

6 months ago
treeherder
Filed by: philringnalda [at] gmail.com

https://treeherder.mozilla.org/logviewer.html#?job_id=89323822&repo=mozilla-inbound

https://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-inbound-macosx64/1491511832/mozilla-inbound_yosemite_r7_test-gtest-bm136-tests1-macosx-build1215.txt.gz
Network intermittent? Looks like single one so far. Let's keep an eye.
Rank: 25
Priority: -- → P2

Comment 2

6 months ago
While I don't understand why the normal active -> passive TCP connections never succeeded, one very interesting thing is that both end of the connection claimed to use the same SO port number:

0-P1:stream0 initialized: candidate:2 1 TCP 2105508095 10.26.58.55 63383 typ host tcptype passive 
0-P1:stream0 initialized: candidate:2 1 TCP 2105524479 10.26.58.55 9 55921 typ host tcptype active 
0-P1:stream0 initialized: candidate:2 1 TCP 2105491711 10.26.58.55 55246 typ host tcptype so

0-P2:stream0 initialized: candidate:2 1 TCP 2105508095 10.26.58.55 51820 typ host tcptype passive 
0-P2:stream0 initialized: candidate:2 1 TCP 2105524479 10.26.58.55 9 56262 typ host tcptype active 
0-P2:stream0 initialized: candidate:2 1 TCP 2105491711 10.26.58.55 55246 typ host tcptype so

And when P1 and P2 tried to use their SO candidates they failed immediately. Now I don't know if hair pinning on regular OS is supported or not.

The question here: does this test normally succeed via the SO candidates (and only failed this one time, because both picked the same port number), because the active -> passive never succeeds?

Comment 3

3 months ago
1 failures in 718 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=1354419&startday=2017-06-26&endday=2017-07-02&tree=all

Comment 4

2 months ago
1 failures in 720 pushes (0.001 failures/push) were associated with this bug in the last 7 days.   

Repository breakdown:
* mozilla-inbound: 1

Platform breakdown:
* osx-cross: 1

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

Comment 5

2 months ago
1 failures in 822 pushes (0.001 failures/push) were associated with this bug in the last 7 days.   

Repository breakdown:
* try: 1

Platform breakdown:
* osx-10-10: 1

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

Comment 6

2 months ago
1 failures in 1008 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=1354419&startday=2017-07-24&endday=2017-07-30&tree=all

Comment 7

2 months ago
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:
* linux32: 1

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

Comment 8

21 days ago
1 failures in 939 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=1354419&startday=2017-08-28&endday=2017-09-03&tree=all
Mass change P2->P3 to align with new Mozilla triage process.
Priority: P2 → P3
Bulk priority update of open intermittent test failure bugs. 

P3 => P5

https://bugzilla.mozilla.org/show_bug.cgi?id=1381960
Priority: P3 → P5
2 failures in 1032 pushes (0.002 failures/push) were associated with this bug in the last 7 days.    

Repository breakdown:
* mozilla-inbound: 2

Platform breakdown:
* osx-10-10: 2

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1354419&startday=2017-09-11&endday=2017-09-17&tree=all
You need to log in before you can comment on or make changes to this bug.