#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 devans@…): * cc: cal@… (added) Comment: Replying to [comment:2 ryandesign@…]:
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. 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. 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.
-- Ticket URL: <https://trac.macports.org/ticket/52543#comment:3> MacPorts <https://www.macports.org/> Ports system for the Mac operating system