1431655 - Logs of jobs which exceeded runtime ends abruptly, doesn't show 'Aborting task - max run time exceeded!' anymore

Status: RESOLVED DUPLICATE of bug 1457694

(Taskcluster :: Workers, defect)

Description

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

If a job exceeded its maximum runtime, the "'Aborting task - max run time exceeded!" got added at the end of the log together with some other meta information.

https://treeherder.mozilla.org/logviewer.html#?job_id=157383000&repo=autoland is ending abruptly without any indication that it exceeded the 1h run time limit defined at https://dxr.mozilla.org/mozilla-central/rev/e4107773cffb1baefd5446666fce22c4d6eb0517/taskcluster/ci/test/mochitest.yml#110

This is frequent (for the jobs exceeding the run time limit, and likely either permanent or no issue, depending on the platform/test config) and seems to be a recent regression from January or December.

Comment 1

[Geoff Brown [:gbrown]]

There is some taskcluster logging earlier in the log, embedded in the test output;

...
09:08:51     INFO -  GECKO(528) | --DOMWINDOW == 10 (007F1B80) [pid = 528] [serial = 1229] [outer = 00000000] [url = about:addons]
09:08:51     INFO -  GECKO(528) | --DOMWINDOW == 9 (1022F000) [pid = 528] [serial = 1231] [outer = 00000000] [url = about:addons]
09:08:51     INFO -  GECKO(528) | --DOMWINDOW == 8 (0F765C00) [pid = 528] [serial = 1259] [outer = 00000000] [url = about:blank]
[taskcluster 2018-01-19T09:08:52.891Z]   Exit Code: 0
[taskcluster 2018-01-19T09:08:52.891Z]   User Time: 0s
[taskcluster 2018-01-19T09:08:52.891Z] Kernel Time: 31.2002ms
[taskcluster 2018-01-19T09:08:52.891Z]   Wall Time: 59m56.8388497s
[taskcluster 2018-01-19T09:08:52.891Z] Peak Memory: 3375104
[taskcluster 2018-01-19T09:08:52.891Z]      Result: IDLENESS_LIMIT_EXCEEDED
[taskcluster 2018-01-19T09:08:52.891Z] === Task Finished ===
[taskcluster 2018-01-19T09:08:52.891Z] Task Duration: 59m56.8578528s
09:08:56     INFO -  GECKO(528) | Completed ShutdownLeaks collections in process 528
09:08:56     INFO -  1118 INFO TEST-START | Shutdown
09:08:56     INFO -  1119 INFO Browser Chrome Test Summary
...

Comment 2

[Intermittent Failures Robot]

4 failures in 735 pushes (0.005 failures/push) were associated with this bug in the last 7 days.    

Repository breakdown:
* mozilla-central: 3
* mozilla-inbound: 1

Platform breakdown:
* windows10-64-ccov: 3
* osx-10-10: 1

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1431655&startday=2018-01-29&endday=2018-02-04&tree=all

Comment 3

[Intermittent Failures Robot]

2 failures in 685 pushes (0.003 failures/push) were associated with this bug in the last 7 days.    

Repository breakdown:
* mozilla-central: 2

Platform breakdown:
* windows2012-32: 2

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

Comment 4

[Intermittent Failures Robot]

1 failures in 831 pushes (0.001 failures/push) were associated with this bug in the last 7 days.    

Repository breakdown:
* mozilla-central: 1

Platform breakdown:
* windows10-64-ccov: 1

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1431655&startday=2018-02-26&endday=2018-03-04&tree=all

Comment 5

[Intermittent Failures Robot]

1 failures in 814 pushes (0.001 failures/push) were associated with this bug in the last 7 days.    

Repository breakdown:
* mozilla-inbound: 1

Platform breakdown:
* windows7-32: 1

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1431655&startday=2018-03-12&endday=2018-03-18&tree=all

Comment 6

[Intermittent Failures Robot]

3 failures in 782 pushes (0.004 failures/push) were associated with this bug in the last 7 days.    

Repository breakdown:
* mozilla-inbound: 3

Platform breakdown:
* windows10-64: 2
* windows7-32: 1

For more details, see:
https://treeherder.mozilla.org/intermittent-failures.html#/bugdetails?bug=1431655&startday=2018-04-16&endday=2018-04-22&tree=trunk

Comment 7

[Dustin J. Mitchell [:dustin] (he/him)]

I strongly suspect this is a dupe of bug 1457694, as the symptoms were very similar.