build-webkittestrunner has been failing on the Mac bots since somewhere between r100471 and r100492. build-webkittestrunner succeeded and tests ran: http://build.webkit.org/builders/SnowLeopard%20Intel%20Release%20%28WebKit2%20Tests%29/builds/15949 build-webkittestrunner failed and no tests ran: http://build.webkit.org/builders/SnowLeopard%20Intel%20Release%20%28WebKit2%20Tests%29/builds/15950
r100488 seems the most likely culprit: http://trac.webkit.org/changeset/100488
It's too bad that NRWT doesn't show us the build log!
Well, that's intentional. :) But I agree, it should show us the build log in verbose mode (which the bots use).
The Debug bot shows the same thing: r100471: good http://build.webkit.org/builders/SnowLeopard%20Intel%20Debug%20%28WebKit2%20Tests%29/builds/2480 r100492: bad http://build.webkit.org/builders/SnowLeopard%20Intel%20Debug%20%28WebKit2%20Tests%29/builds/2481
Are there build failure logs available anywhere? (In reply to comment #1) > r100488 seems the most likely culprit: > > http://trac.webkit.org/changeset/100488
No. See bug 71160.
Looks like Lion Intel Debug (WebKit2 Tests) is fine. Maybe there's a compiler error that affects GCC but not clang?
(In reply to comment #7) > Looks like Lion Intel Debug (WebKit2 Tests) is fine. Maybe there's a compiler error that affects GCC but not clang? Lion Intel Release (WebKit2 Tests) is now using Clang (thanks to Xcode 4.2), and it's still failing: http://build.webkit.org/builders/Lion%20Intel%20Release%20%28WebKit2%20Tests%29/builds/2136/steps/layout-test/logs/stdio
Looks like Lion Intel Debug (WebKit2 Tests) is now failing too. I guess the newer Clang in Xcode 4.2 is being more strict.
Hooray, we have build output! http://build.webkit.org/builders/Lion%20Intel%20Release%20%28WebKit2%20Tests%29/builds/2144/steps/layout-test/logs/stdio
Here's more: http://build.webkit.org/builders/Lion%20Intel%20Debug%20%28WebKit2%20Tests%29/builds/2062/steps/layout-test/logs/stdio
Both of those logs look like the problem is local to the bots. A clean build should fix it.
I've deleted the WebKitBuild directories on the two affected bots. Let's see what happens.
Looks like a clean build didn't fix it: http://build.webkit.org/builders/Lion%20Intel%20Release%20%28WebKit2%20Tests%29/builds/2146/steps/layout-test/logs/stdio
I'll try deleting precompiled headers on these machines too.
That seems to have done the trick: http://build.webkit.org/builders/Lion%20Intel%20Release%20%28WebKit2%20Tests%29/builds/2147/steps/layout-test/logs/stdio I'll wait for the other bot before closing this.
The other bot looks good too: http://build.webkit.org/builders/Lion%20Intel%20Debug%20%28WebKit2%20Tests%29/builds/2065/steps/layout-test/logs/stdio Yay!