Looks like all the added jobs are failing due to timeouts: https://treeherder.mozilla.org/#/jobs?repo=try&collapsedPushes=508078%2C507437%2C508091%2C508292%2C508873%2C508874%2C509967&selectedJob=257146984&revision=664c3452e3556ebe39b0df4a7e28df1ab9a5797d

[taskcluster:error] Aborting task...
...
[taskcluster:error] Task aborted - max run time exceeded

It looks like the test hung for at least 28 minutes. Was there anything in the push that could have caused that?

Things would crash or look wrong, but I don't expect this change to affect the timing (this much).

I'm not sure if it is related to you changes, but it does appear that the test failed inside the task here. This may be an issue with your change or with the test runner, but I'm guessing it isn't related to how the task was triggered.

Another try from yesterday - same timeouts:
https://treeherder.mozilla.org/#/jobs?repo=try&revision=624db5cb38edd9e11df560ec161638c255bc0576

The priority flag is not set for this bug.
:rwood, could you have a look please?

For more information, please visit auto_nag documentation.

Hi Dzmitry, is this still an issue? Thanks.

Yep, looks like it's still there - https://treeherder.mozilla.org/#/jobs?repo=try&revision=4801c76895102c7a309a752025b59e2bd84f4098