1439359 - Intermittent Android-reftest application ran for longer than allowed maximum time

Status: RESOLVED DUPLICATE of bug 1433163

(Testing :: Reftest, defect, P5)

Description

[Treeherder Bug Filer]

Filed by: rgurzau [at] mozilla.com

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

https://queue.taskcluster.net/v1/task/FFb7BxL0QsGVk8CzIVavVg/runs/0/artifacts/public/logs/live_backing.log

https://hg.mozilla.org/mozilla-central/raw-file/tip/layout/tools/reftest/reftest-analyzer.xhtml#logurl=https://queue.taskcluster.net/v1/task/FFb7BxL0QsGVk8CzIVavVg/runs/0/artifacts/public/logs/live_backing.log&only_show_unexpected=1

[task 2018-02-19T12:14:43.795Z] 12:14:43     INFO -  org.mozilla.fennec_aurora still alive after SIGABRT: waiting...
[task 2018-02-19T12:14:48.919Z] 12:14:48  WARNING -  TEST-UNEXPECTED-FAIL | http://10.0.2.2:8888/tests/layout/reftests/position-dynamic-changes/vertical/topA-heightN-bottomN.html?margin_parent == http://10.0.2.2:8888/tests/layout/reftests/position-dynamic-changes/vertical/topA-heightN-bottomN-ref.html?margin_parent | application ran for longer than allowed maximum time
[task 2018-02-19T12:14:48.919Z] 12:14:48     INFO -  INFO | automation.py | Application ran for: 1:30:32.088155

Comment 1

[Sebastian Hengst [:aryx] (needinfo me if it's about an intermittent or backout)]

Such reftest failures on Android are quite frequent (search for "application ran for longer than allowed maximum time").

This test has:

[task 2018-02-19T12:14:38.684Z] 12:14:38     INFO -  REFTEST TEST-START | http://10.0.2.2:8888/tests/layout/reftests/position-dynamic-changes/vertical/topA-heightN-bottomN.html?margin_parent == http://10.0.2.2:8888/tests/layout/reftests/position-dynamic-changes/vertical/topA-heightN-bottomN-ref.html?margin_parent
[task 2018-02-19T12:14:38.684Z] 12:14:38     INFO -  REFTEST TEST-LOAD | http://10.0.2.2:8888/tests/layout/reftests/position-dynamic-changes/vertical/topA-heightN-bottomN.html?margin_parent | 284 / 314 (90%)
[task 2018-02-19T12:14:39.521Z] 12:14:39     INFO -  Browser unexpectedly found running. Killing...
[task 2018-02-19T12:14:39.523Z] 12:14:39     INFO -  REFTEST TEST-INFO | started process screentopng
[task 2018-02-19T12:14:39.943Z] 12:14:39     INFO -  REFTEST TEST-INFO | screentopng: exit 0
[task 2018-02-19T12:14:43.795Z] 12:14:43     INFO -  org.mozilla.fennec_aurora still alive after SIGABRT: waiting...
[task 2018-02-19T12:14:48.919Z] 12:14:48  WARNING -  TEST-UNEXPECTED-FAIL | http://10.0.2.2:8888/tests/layout/reftests/position-dynamic-changes/vertical/topA-heightN-bottomN.html?margin_parent == http://10.0.2.2:8888/tests/layout/reftests/position-dynamic-changes/vertical/topA-heightN-bottomN-ref.html?margin_parent | application ran for longer than allowed maximum time

The run time limit is 2 hours: https://dxr.mozilla.org/mozilla-central/rev/dc70d241f90df43505ece5ac12261339e9694c50/taskcluster/ci/test/reftest.yml#114

According to the log, it ran for 104 minutes:
Start	Mon Feb 19, 11:31:10
End	Mon Feb 19, 13:15:30

Geoff, can you shed some light on the reason why this gets terminated? Thanks.

Comment 2

[Geoff Brown [:gbrown]]

I am aware of the problem and trying to sort it out in bug 1433163 (tried on Friday, but backed out!)...hope to get this fixed soon.

Comment 4

[Intermittent Failures Robot]

5 failures in 675 pushes (0.007 failures/push) were associated with this bug in the last 7 days.    

Repository breakdown:
* autoland: 2
* try: 1
* mozilla-inbound: 1
* mozilla-beta: 1

Platform breakdown:
* android-4-3-armv7-api16: 5

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1439359&startday=2018-02-19&endday=2018-02-25&tree=all