1308336 - Try removing intermittent testUnifiedTelemetryClientId fix once Android tests run on TC

Status: RESOLVED WONTFIX

(Firefox for Android Graveyard :: Testing, defect, P3)

Description

[Michael Comella (:mcomella) [NI reported issues only: ex-Mozilla]]

In bug 1294643 comment 24, gbrown pushed a patch that (delightfully! :) reduced the intermittent failure rate of testUnifiedTelemetryClientId but reduced the test's coverage (as per bug 1294643 comment 28). Notably the failures only occurred on BuildBot & not TaskCluster – once the Android tests moved to TC (bug 1295188), we'd like to try removing this patch.

Comment 1

[Michael Comella (:mcomella) [NI reported issues only: ex-Mozilla]]

fwiw, Geoff explained how BuildBot & TaskCluster runs are different:

(In reply to Geoff Brown [:gbrown] from bug 1294643 comment #34)
> > Geoff, do you know what's different between the configurations?
> 
> Yes - speed! Robocop tests run on a faster (more memory, more cores) aws
> instance type when run from taskcluster. (That is not the case for most test
> types migrated from buildbot to taskcluster, but I found that robocop was
> struggling on taskcluster until I bumped up the aws capabilities.)
> 
> So, that might be a clue: Maybe the test fails when some change/response/etc
> is delayed?

Note that we're still having similar failures with bug 1295188.

Comment 2

[Geoff Brown [:gbrown]]

Mass closing Firefox for Android :: Testing bugs with no progress in 2017.

If this bug is important to you, please re-open.