There's probably not a whole we can do here. This error means that for whatever reason, things ran a bit slower than usual. If there were a specific platform / suite / chunk that were consistently exceeding the `maxruntime` then we could easily fix it by increasing chunks or bumping up the `maxruntime`. But because the distribution of platforms is very evenly spread out there aren't any clear actionable signals to work on here. Fwiw, I'd tend to treat each platform this error happens on as a separate issue. So grouping all `reftest` tasks under a single bug is misleading in terms of how bad of an intermittent this is.
Bug 1420394 Comment 92 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
There's probably not a whole we can do here. This error means that for whatever reason (slow network, background processes eating CPU, etc), things ran a bit slower than usual. If there were a specific platform / suite / chunk that were consistently exceeding the `maxruntime` then we could easily fix it by increasing chunks or bumping up the `maxruntime`. But because the distribution of platforms is very evenly spread out there aren't any clear actionable signals to work on here. Fwiw, I'd tend to treat each platform this error happens on as a separate issue. So grouping all `reftest` tasks under a single bug is misleading in terms of how bad of an intermittent this is.