Travis CI for Mac fails with "Your Xcode (6.1) is outdated"

[jay]

curl/curl mac ci recently failed with "Your Xcode (6.1) is outdated". Our travis.yml uses 'osx'. I read in your doc that other versions can be used, but I'm not sure if this is a bug that the standard 'osx' doesn't appear to be working since our most recent ci run.

Warning: You are using macOS 10.9.
We (and Apple) do not provide support for this old version.
You may encounter build failures or other breakages.
Please create pull-requests instead of filing issues.
Error: Your Xcode (6.1) is outdated
Please update to Xcode 6.2.
Xcode can be updated from the App Store.

/cc @bagder @snikulov

[jay]

This might be brew related?
The command "if [ "$TRAVIS_OS_NAME" == "osx" ]; then brew install openssl libidn rtmpdump libssh2 c-ares libmetalink libressl nghttp2; fi" failed and exited with 1 during .

If we are in the wrong my apologies I don't work with OS X I'm not sure what is supposed to happen here.

edit: found a brew issue that could be it Homebrew/brew#1096

/cc @DomT4

[DomT4]

Should be fixed now? I reverted the problematic commit a few hours ago. There's a replacement pending with a special exemption for Travis, but not merged yet.

Sent from my iPhone

On 23 Sep 2016, at 05:02, Jay Satiro notifications@github.com wrote:

This might be brew related?
The command "if [ "$TRAVIS_OS_NAME" == "osx" ]; then brew install openssl libidn rtmpdump libssh2 c-ares libmetalink libressl nghttp2; fi" failed and exited with 1 during .

If we are in the wrong my apologies I don't work with OS X I'm not sure what is supposed to happen here.

/cc @DomT4

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

[SlySven]

Might be related, but I took the opportunity to try to force my Projects dual-OS built to use the next XCode version up with a osx_image: beta-xcode6.2 but I can't see how to insert it into the build matrix, I thought this would work:

language: cpp
os:
  - osx
  - linux
compiler:
  - gcc
  - clang
env:
  - Q_OR_C_MAKE=qmake
  - Q_OR_C_MAKE=cmake
matrix:
# The previous default of osx_image: beta-xcode6.1 no longer works, certainly as of 2016-09-22! - SlySven
  include:
    - os: osx
      osx_image: beta-xcode6.2
# Something goes wrong internally in Qt (5.0.2) for CMake Clang builds on Linux
  allow_failures:
    - os: linux
      compiler: clang
      env: Q_OR_C_MAKE=cmake

However as well as the expected matrix of 2(oss) x 2(compiler) x 2(env) but with the osx ones WITHOUT the osx_image value I got an extra one WITH the latter but the Job Config for that reads:

{
  "language": "cpp",
  "os": "osx",
  "compiler": [
    "gcc",
    "clang"
  ],
  "env": "Q_OR_C_MAKE=qmake Q_OR_C_MAKE=cmake",

some install and other irrelevant entries omitted!

  "group": "stable",
  "dist": "precise",
  "osx_image": "beta-xcode6.2"
}

A previous test reveals that a os: linux configuration gets confused by a presence of an osx_image setting so how do we set the osx_image parameter for just the os: osx case? I will try again later to verify that os:linux vs. osx_image clash because I may have had an error in the .travis.yml file then, but the documentation on dual platforms is not as clear as it could be IMHO.

[jay]

Should be fixed now? I reverted the problematic commit a few hours ago.

It's working now, thanks Dominyk. Is this a travis issue? I don't understand what Stephen is talking about, should I close this or leave it open for them?

[DomT4]

Stephen possibly needs to file an Issue independently of this; I don't think it's related to the problem you raised unless I'm missing something.

It's not a Travis issue per se. We're trying to get users to run the latest Xcode and/or CLT available on their platform because that's what we test and build against and that's what we know works, or doesn't work in some cases. It makes builds & troubleshooting more consistent for all parties involved.

However, Travis is locked to specific Xcode releases with no current way for users to say "Hey, I'd like to run Xcode 8 on OS X 10.11", which effectively killed a good chunk of Travis builds for that very short period. I've since re-added the problematic change, but I've wrapped it in a protective cushion so that Travis or anyone with HOMEBREW_DEVELOPER set isn't impacted.

The implementation will likely be tweaked further in future, but going forwards I'll try to make sure we're a bit more careful to consider the Travis situation & users of Travis not having an Xcode upgrade path available to them.

[BanzaiMan]

I think this can be closed.