Moth causes problems for treeherder since it assumes that there is only one error summary per job, and that job produces two. This leads to bad data, and slowness as tasks are retried. It seems like this split was made for debug builds in the gecko 44 timeframe. Is there any reason we can't do it for opt builds as well?

Armen: I'm not sure if you're the best person to ask, but is there some reason not to split these jobs out? If you aren't the best person to ask, do you know who is?

jmaher and I worked on this together. My vague recollection was that there were too many Linux builders at the time but I can't tell [1] At the same time, we're going to be adding a new gpu jobs which is a collection of multiple harnesses. What could be done for Treeherder and these kind of jobs to work better together instead of splitting them up? [1] https://bugzilla.mozilla.org/show_bug.cgi?id=1211889#c29

Do we know if the builder situation has improved in the interim e.g. by removing project branches? This could work better in buildbot if we stored some extra information with the job e.g. the error summary filename. But this is the only job we have that requires that, so it's very annoying to make the backend more complex just to support this single oddball.

I don't see a problem with doing this- I believe as we just turned off a lot of linux64 builders we have room- :jgraham, feel free to polish up our old patch!

> This could work better in buildbot if we stored some extra information with the job e.g. the error summary filename. Would you mind ellaborating more about this? I'm happy to improve this if the gpu job will have the same problems.