Android 4.3 Debug reftests of all types are slow, but the J7 job takes it to a new level. With current chunking, the other Android 4.3 Debug js-reftests complete in about 60 minutes, but J7 almost always exceed 100 minutes and frequently times out with "application ran for longer than allowed maximum time".

A few very-slow tests in J7 caught my eye, from bug 360969 (added almost a decade ago): js1_5/Regress/regress-360969-01.js ... js1_5/Regress/regress-360969-06.js Each of these tests repeat a simple js declaration 2^17 (100000+) times. These 6 tests complete in 30+ minutes on Android 4.3 Debug. (About 10 minutes on Android 4.3 Opt; 90 seconds on Linux Debug; 40 seconds on Linux Opt.) These tests (and others) have been identified as long-running before; see http://hg.mozilla.org/mozilla-central/annotate/1a157155a4fe/js/src/devtools/automation/cgc-jstests-slow.txt and https://bugzilla.mozilla.org/show_bug.cgi?id=1101662#c2.

Closer review of Android 4.3 Debug J7 also found: js1_5/GC/regress-203278-2.js - takes about 4 minutes js1_5/Regress/regress-416628.js - about 3 minutes js1_5/Regress/regress-244470.js - about 2 minutes

Skipping regress-360969-01.js .. regress-360969-06.js is sufficient to reduce total time for J7 to under 80 minutes: https://treeherder.mozilla.org/#/jobs?repo=try&revision=0c727ae04d61&exclusion_profile=false I don't think there is much incremental value in running these tests on Android Debug vs Android Opt or desktop Debug - let's just skip them.

(In reply to Geoff Brown [:gbrown] from comment #3) > I don't think there is much incremental value in running these tests on > Android Debug vs Android Opt or desktop Debug - let's just skip them. Skip them on Android Debug, that is.