1884667 - Using fresh profiles in android pageload tests causes a very high intermittent failure rate

Status: NEW

(Testing :: Raptor, defect, P2)

Description

[Greg Mierzwinski [:sparky]]

For some reason, using fresh profiles instead of conditioned profiles that are created prior to the test running causes the android pageload tests to fail intermittently at a very high rate. It looks like there are crashes that happen, but we're unable to get more information about them as the crash dumps aren't being found/saved.

Comment 1

[Joel Maher ( :jmaher ) (UTC -8)]

at lambdatest it seems that every other run of the conditioned profile fails. If I skip this, tests run reliably- of course at scale of thousands of tasks it might be a different story. While I would like to figure out the condprof issues, I wonder if it is still needed?

Comment 2

[Joel Maher ( :jmaher ) (UTC -8)]

not related to android, but bug 1716416 has failures where we fail to generate the conditioned profile on desktop due to timeout of connecting via marionette.