See https://tbpl.mozilla.org/php/getParsedLog.php?id=12718710&tree=Mozilla-Inbound&full=1 and https://tbpl.mozilla.org/php/getParsedLog.php?id=12719085&tree=Mozilla-Aurora&full=1 and https://tbpl.mozilla.org/php/getParsedLog.php?id=12718824&tree=Mozilla-Aurora&full=1 Dunno whether they got left with winrm.exe after bug 727551, or didn't get a workable rm.exe back, but to my surprise, failure to rm equals lots of failures on the next run, at least for some suites.

Just those three.

I logged into these three XP machines over VNC, they were enabled in slavealloc as of the time I checked. I found rm-new.exe in C:\mozilla-build\msys\bin\ which corresponded to the size of rm.exe on my machine, as well as had a creation date in 2010, I renamed this to rm.exe (which was missing entirely) Leaving open until we can verify they are sane, and CC'ing coop (who deployed this) and last weeks and this weeks buildduty.

Jobs have been taken on these slaves since then, and the rm.exe is working right. Resolving.