Opened 12 years ago

Closed 12 years ago

#38410 closed defect (fixed)

Lion buildbot disconnected while building textmate2 @2.0.9395

Reported by: ryandesign (Ryan Carsten Schmidt) Owned by: wsiegrist@…
Priority: Normal Milestone:
Component: server/hosting Version:
Keywords: Cc: neverpanic (Clemens Lang)
Port: textmate2

Description

https://build.macports.org/builders/buildports-lion-x86_64/builds/9347/steps/compile/logs/stdio says:

remoteFailed: [Failure instance: Traceback (failure with no frames): <class 'twisted.internet.error.ConnectionLost'>: Connection to the other side was lost in a non-clean fashion.

Subsequent commits are building on the other two buildbots but not on the Lion buildbot.

Change History (6)

comment:1 Changed 12 years ago by wsiegrist@…

Resolution: fixed
Status: newclosed

Fixed.

comment:2 Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)

Cc: cal@… added
Port: textmate2 added
Resolution: fixed
Status: closedreopened
Summary: Lion buildbot disconnectedLion buildbot disconnected while building textmate2 @2.0.9395

It happened again, at exactly the same place building the same port textmate2 @2.0.9395 (step "[155/157]"). Has the Lion buildbot experienced a kernel panic or what is the symptom?

I tried building textmate2 on my Lion machine with Xcode 4.3.3 and got:

Error: On Mac OS X 10.7, textmate2 2.0.9395 requires Xcode 4.4 or later but you have Xcode 4.3.3.
Error: See http://guide.macports.org/chunked/installing.xcode.html for download links.
Error: org.macports.extract for port textmate2 returned: incompatible Xcode version

This is because of this line in the portfile:

minimum_xcodeversions   {11 4.4}

This was added in r98375 to fix #36443 because textmate2 requires the 10.8 SDK even on 10.7.

If I remove the minimum_xcodeversions line, I get:

/usr/bin/clang is too old to build this project.

Please see README.md for build instructions.

I remember that awhile ago the Lion buildbot was using Xcode 4.3.3. It seems it has been updated since then (maybe when it was converted from a standalone server to a virtual machine?) but perhaps the command line tools were not updated and are thus still at the version of Xcode 4.3.3? Bill, what does running clang -v on the Lion buildbot say? What about xcodebuild -version?

The port should probably use the compiler_blacklist_versions portgroup to blacklist old clangs that are known not to work, so that any users who have updated Xcode but not its command line tools (which is quite a common occurrence) do not run into problems, or at least encounter a friendlier or earlier error message.

I will also test on a Mountain Lion Mac that still has Xcode 4.5.2 and its Apple clang version 4.1 (tags/Apple/clang-421.11.66) (based on LLVM 3.1svn) but it will take some time to build boost first.

comment:3 in reply to:  2 Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)

Replying to ryandesign@…:

I will also test on a Mountain Lion Mac that still has Xcode 4.5.2 and its Apple clang version 4.1 (tags/Apple/clang-421.11.66) (based on LLVM 3.1svn) but it will take some time to build boost first.

I filed #38422 for the way that this failed to build.

comment:4 Changed 12 years ago by wsiegrist@…

It panicked. The slave had been running Xcode 4.5.2. I updated the slaves, including Xcode 4.6.1. Let's see if it still reproduces.

comment:5 Changed 12 years ago by wsiegrist@…

It reproduced. I'm working on a fix.

comment:6 Changed 12 years ago by wsiegrist@…

Resolution: fixed
Status: reopenedclosed

The slave has been patched to not panic. Now it fails like #38422.

Note: See TracTickets for help on using tickets.