sheriffbot said this recently: <sheriffbot> ossy: http://trac.webkit.org/changeset/89814 might have broken Windows XP Debug (Tests) <sheriffbot> New failures: fast/text/midword-break-before-surrogate-pair.html, svg/custom/linking-uri-01-b.svg This seems obviously wrong. Here are the failing tests for r89813 and r89814: r89813 http://build.webkit.org/results/Windows%20XP%20Debug%20%28Tests%29/r89813%20(30033)/results.html fast/text/midword-break-before-surrogate-pair.html fast/workers/storage/change-version-sync.html fast/workers/storage/empty-statement-sync.html svg/custom/linking-uri-01-b.svg r89814 http://build.webkit.org/results/Windows%20XP%20Debug%20%28Tests%29/r89814%20(30034)/results.html fast/text/midword-break-before-surrogate-pair.html svg/custom/linking-uri-01-b.svg The two tests sheriffbot mentioned were already failing in r89813, so it shouldn't have blamed r89814 for breaking them.
Was there a hiccup before r89813? Did the master restart or we skip a build? If it had a skipped built it would have counted them as passing.
According to http://build.webkit.org/results/Windows%20XP%20Debug%20%28Tests%29/, This is the previous build: r89808: http://build.webkit.org/results/Windows%20XP%20Debug%20%28Tests%29/r89808%20%2830032%29/results.html fast/text/midword-break-before-surrogate-pair.html fast/workers/storage/change-version-sync.html fast/workers/storage/empty-statement-sync.html svg/custom/linking-uri-01-b.svg So it looks like those were already failing. I'll look at hte log to see if we had a master restart or sherriff-bot restart or similar in between.
There are two machines servicing that buildbot queue, but I don't see them giving conflicting results here. I think something may be funny in sheriffbot's head here.
You can see all the recent builds here yourself: http://build.webkit.org/builders/Windows%20XP%20Debug%20%28Tests%29?numbuilds=50 (at least for the next 24 hours or so).