Opened 5 years ago

Closed 5 years ago

#59302 closed defect (fixed)

ports-10.6_x86_64-builder: builds are systematically failing due to apparent Xcode issue

Reported by: dbevans (David B. Evans) Owned by: ryandesign (Ryan Carsten Schmidt)
Priority: Normal Milestone:
Component: buildbot/mpbb Version:
Keywords: buildbot ports-10.6_x86_64-builder Cc:
Port:

Description

I'm not sure when this began, but currently on ports-10.6_x86_64-builder. p5.30 builds are systematically failing as follows: 

DEBUG: Starting logging for p5.30-moosex-setonce
DEBUG: Mac OS X 10.6 (darwin/10.8.0) arch i386
DEBUG: MacPorts 2.6.1
DEBUG: Xcode none
DEBUG: SDK 10.6
DEBUG: MACOSX_DEPLOYMENT_TARGET: 10.6
Error: Port p5.30-moosex-setonce requires a full Xcode installation, which was not found on your system.
Error: You can install Xcode from the Mac App Store or https://developer.apple.com/xcode/
Error: Follow https://guide.macports.org/#project.tickets to report a bug.
Error: Processing of port p5.30-moosex-setonce failed
Build of 'p5.30-moosex-setonce' failed.
./mpbb/mpbb: error: `install-port' failed to run successfully

Change History (8)

comment:1 Changed 5 years ago by dbevans (David B. Evans)

Component: ports → buildbot/mpbb

comment:2 Changed 5 years ago by jmroot (Joshua Root)

That code should only trigger if $xcodeversion is "none". Not sure how that would be happening.

comment:3 Changed 5 years ago by ryandesign (Ryan Carsten Schmidt)

Status: assigned → accepted

After a Snow Leopard machine has been online for a time, MacPorts becomes unable to identify the Xcode version. I have been dealing with this problem for years, periodically needing to restart the Snow Leopard build workers to get things working again. We have discussed it before and have not figured out the cause or how to fix it. Under previous versions of MacPorts it would manifest differently, with the "System cc" compiler being selected, which still allowed some ports to build but others would fail. I guess the changes in MacPorts 2.6 mean it will now manifest as an error message about missing Xcode and all ports will fail.

I have stopped the 10.6-x86_64 builder and will keep it offline until the distfiles for all the other builds that are queued have been mirrored (due to #59286). The 10.6-i386 builder is already offline for this reason. I have deleted the failcache entries for p5.30 ports on 10.6-x86_64. I have canceled the remaining p5.30 port builds on 10.6-x86_64 (due to #53587 and #59287).

I will need to reschedule the p5.30 builds on 10.6-x86_64.

Last edited 5 years ago by ryandesign (Ryan Carsten Schmidt) (previous) (diff)

comment:4 Changed 5 years ago by dbevans (David B. Evans)

Sounds good. Thanks for the update.

comment:5 Changed 5 years ago by jmroot (Joshua Root)

The 10.9 builder is caught up, so all the mirroring that will happen has presumably happened. Can we bring the < 10.9 builders back up now?

comment:6 Changed 5 years ago by ryandesign (Ryan Carsten Schmidt)

Yes, I will do that, after I solve #59217.

comment:7 in reply to:  6 Changed 5 years ago by ryandesign (Ryan Carsten Schmidt)

Replying to ryandesign:

I will need to reschedule the p5.30 builds on 10.6-x86_64.

That's all the ports modified by [ff590681e5f5f053c05b80f62ae19ef628fec0f8/macports-ports]. I'm going to wait on this until other queued builds are done, to minimize problems due to #59286 / #53587 / #59287.

comment:8 Changed 5 years ago by ryandesign (Ryan Carsten Schmidt)

Resolution: → fixed
Status: accepted → closed

All was quiet on the 10.6 x86_64 builder, so I restarted it and rescheduled those ports here: ​https://build.macports.org/builders/ports-10.6_x86_64-watcher/builds/2109

Note: See TracTickets for help on using tickets.