Bug 132688

Summary: REGRESSION(r168471): Duplicate builddirs broke master
Product: WebKit Reporter: Carlos Alberto Lopez Perez <clopez>
Component: Tools / TestsAssignee: Nobody <webkit-unassigned>
Status: RESOLVED FIXED    
Severity: Normal CC: cgarcia, commit-queue, lforschler, svillar
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   
Attachments:
Description Flags
Patch none

Carlos Alberto Lopez Perez
Reported 2014-05-08 09:55:44 PDT
After landing r168471 the buildmaster broke. 2014-05-08 09:10:17-0700 [-] Unknown builder 'GTK Linux 64-bit Release' in scheduler 'trunk' 2014-05-08 09:10:17-0700 [-] Unknown builder 'GTK Linux 64-bit Debug' in scheduler 'trunk' 2014-05-08 09:10:17-0700 [-] duplicate builder builddir 'gtk-linux-64-release' 2014-05-08 09:10:17-0700 [-] duplicate builder builddir 'gtk-linux-64-debug' 2014-05-08 09:10:17-0700 [-] Halting master. 2014-05-08 09:10:17-0700 [-] Main loop terminated. 2014-05-08 09:10:17-0700 [-] Server Shut Down. on r168471 https://bugs.webkit.org/show_bug.cgi?id=131358 I configured the builddir for the tests bots to be the same than the build ones. This was intentionally, because we (GTK) build a couple of external dependencies with jhbuild and link webkit to them. And the linking process relies on the full path. But I can workaround it on the buildslaves using symlinks, so is not a problem. I didn't know that the buildmaster will complain about two bots with the same builddir.
Attachments
Patch (2.29 KB, patch)
2014-05-08 10:07 PDT, Carlos Alberto Lopez Perez
no flags
Carlos Alberto Lopez Perez
Comment 1 2014-05-08 10:07:11 PDT
Carlos Garcia Campos
Comment 2 2014-05-08 10:14:50 PDT
Comment on attachment 231075 [details] Patch Ok, let's try again
WebKit Commit Bot
Comment 3 2014-05-08 10:51:11 PDT
Comment on attachment 231075 [details] Patch Clearing flags on attachment: 231075 Committed r168475: <http://trac.webkit.org/changeset/168475>
WebKit Commit Bot
Comment 4 2014-05-08 10:51:14 PDT
All reviewed patches have been landed. Closing bug.
Note You need to log in before you can comment on or make changes to this bug.