#52543: snowleopard-x86_64-legacy buildbot worker: xcodebuild exists but failed to execute -----------------------------+-------------------------- Reporter: ryandesign@… | Owner: ryandesign@… Type: defect | Status: closed Priority: Normal | Milestone: Component: server/hosting | Version: Resolution: fixed | Keywords: Port: | -----------------------------+-------------------------- Changes (by ryandesign@…): * status: new => closed * resolution: => fixed Comment: Not knowing what else to try, I've rebooted this worker. This appears to have helped: [https://build.macports.org/builders/ports-10 .6_x86_64_legacy-builder/builds/7092 build 7092] shows: {{{ DEBUG: Using compiler 'Xcode GCC 4.2' }}} Short of committing a change to the at-spi2-core portfile, I don't know how to get the buildbot to clear the failed build from the failcache. Just forcing a build of at-spi2-core on the buildbot web site will presumably only clear the non-universal build from the failcache, and forcing a build of wine again will not attempt to build at-spi2-core again because it's in the failcache. -- Ticket URL: <https://trac.macports.org/ticket/52543#comment:2> MacPorts <https://www.macports.org/> Ports system for the Mac operating system

#52543: snowleopard-x86_64-legacy buildbot worker: xcodebuild exists but failed to execute -----------------------------+-------------------------- Reporter: ryandesign@… | Owner: ryandesign@… Type: defect | Status: closed Priority: Normal | Milestone: Component: server/hosting | Version: Resolution: fixed | Keywords: Port: | -----------------------------+-------------------------- Comment (by ryandesign@…): Replying to [comment:3 devans@…]:

If I'm looking at the relevant code, it appears that, if you could generate/determine the failcache hash for the given port and variant, you could manually remove the corresponding entry from the failcache directory. This is essentially what [http://svn.macports.org/repository/macports/contrib/mp-buildbot/functions failcache_success() in contrib/mp-buildbot/functions] does.

True. From [https://build.macports.org/builders/ports-10.6_x86_64_legacy- builder/builds/7085 build 7085]: {{{ port at-spi2-core +universal 942bd1ec04930577a3b0c8857ada6c840e6f793a2a65f0a52bfcb03b624f6c7b previously failed in build https://build.macports.org/builders/ports-10 .6_x86_64_legacy-builder/builds/7064 }}} I removed that file from the failcache and started [https://build.macports.org/builders/ports-10.6_x86_64_legacy- builder/builds/7107 build 7107].

Maybe it would be useful for admin purposes to have a tool that would do this or, even more elegantly, add something to an appropriate buildbot display that would allow someone with login access to do this for a given failed build.

I think the intention is that you can force a new build of the port, which ignores the failcache. The problem is that here the failed build is universal, and we don't have a way to specify variants when forcing a build. Maybe we should add that, though I'm wary of letting people build arbitrary variants on the buildbot. Maybe we can add checkboxes for the two specific variants that we're considering making the buildbot build automatically: universal and quartz. Though I'm not sure how much we can customize the web pages. -- Ticket URL: <https://trac.macports.org/ticket/52543#comment:4> MacPorts <https://www.macports.org/> Ports system for the Mac operating system