(In reply to Nicolas B. Pierron [:nbp] from comment #15) > (In reply to Agi Sferro | :agi | ni? for questions | ⏰ PST | he/him from comment #14) > > I see, do you see the same timeouts if you rebase to master? we aren't seeing this intermittent anymore from what I can tell. > > > > If you do see them, can you link a try run? > > I send it to try once more, I did not noticed any more timeout being reported. On the other hand the test case `org.mozilla.geckoview.test.crash.ParentCrashTest#crashParent` does not seems to be executed anymore in most configuration where it used to timeout. Oh man! What you were seeing is Bug 1729561, which I found while looking at this. The `stack=org.junit.AssumptionViolatedException: got: <true>, expected: <false>` is expected, it's the way we "skip" tests on Android.(In reply to Nicolas B. Pierron [:nbp] from comment #16) > (In reply to Nicolas B. Pierron [:nbp] from comment #15) > > (In reply to Agi Sferro | :agi | ni? for questions | ⏰ PST | he/him from comment #14) > > > I see, do you see the same timeouts if you rebase to master? we aren't seeing this intermittent anymore from what I can tell. > > > > > > If you do see them, can you link a try run? > > > > https://treeherder.mozilla.org/jobs?repo=try&revision=40c5c5f617af8b9d4bb5ca2269cf42dffb907932 > > Apparently this bug got reproduced on this try push with the `gv-junit` test suite on `android-em-7-0-x86_64-lite-qr opt` OK good. I'll see if I can guess what's the problem there.
Bug 1615203 Comment 17 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to Nicolas B. Pierron [:nbp] from comment #15) > (In reply to Agi Sferro | :agi | ni? for questions | ⏰ PST | he/him from comment #14) > > I see, do you see the same timeouts if you rebase to master? we aren't seeing this intermittent anymore from what I can tell. > > > > If you do see them, can you link a try run? > > I send it to try once more, I did not noticed any more timeout being reported. On the other hand the test case `org.mozilla.geckoview.test.crash.ParentCrashTest#crashParent` does not seems to be executed anymore in most configuration where it used to timeout. Oh man! What you were seeing is Bug 1729561, which I found while looking at this. The `stack=org.junit.AssumptionViolatedException: got: <true>, expected: <false>` is expected, it's the way we "skip" tests on Android. (In reply to Nicolas B. Pierron [:nbp] from comment #16) > > (In reply to Agi Sferro | :agi | ni? for questions | ⏰ PST | he/him from comment #14) > > > I see, do you see the same timeouts if you rebase to master? we aren't seeing this intermittent anymore from what I can tell. > > > > > > If you do see them, can you link a try run? > > > > https://treeherder.mozilla.org/jobs?repo=try&revision=40c5c5f617af8b9d4bb5ca2269cf42dffb907932 > > Apparently this bug got reproduced on this try push with the `gv-junit` test suite on `android-em-7-0-x86_64-lite-qr opt` OK good. I'll see if I can guess what's the problem there.