# Mac OS build failing. No error messages but multiple warnings for Apple old code

**URL:** <https://travis-ci.community/t/mac-os-build-failing-no-error-messages-but-multiple-warnings-for-apple-old-code/11322>\
**Category:** R\
**Created:** [March 19, 2021, 7:56pm UTC](https://travis-ci.community/t/mac-os-build-failing-no-error-messages-but-multiple-warnings-for-apple-old-code/11322 "2021-03-19T19:56:16Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![rmsharp](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/rmsharp/32/6289_2.png) [@rmsharp](https://travis-ci.community/u/rmsharp)\
**Post date:** [March 19, 2021, 7:56pm UTC](https://travis-ci.community/t/mac-os-build-failing-no-error-messages-but-multiple-warnings-for-apple-old-code/11322/1 "2021-03-19T19:56:16Z")

</div>

@jeroen and @jimhester my build at  
[https://travis-ci.org/github/rmsharp/nprcgenekeepr/jobs/763492781](https://travis-ci.org/github/rmsharp/nprcgenekeepr/jobs/763492781)  
is failing with the message “No output has been received in the last 10m0s, this potentially indicates a stalled build or something wrong with the build itself.”

Prior to that the following warnings were issued:  
==\> Installing java…  
67 Warning: You are using macOS 10.13.  
68 We (and Apple) do not provide support for this old version.  
69 You will encounter build failures with some formulae.  
Warning: Your Xcode (9.4.1) is outdated.  
76 Please update to Xcode 10.1 (or delete it).  
77 Xcode can be updated from the App Store.  
79 Warning: A newer Command Line Tools release is available.  
80 Update them from Software Update in the App Store or run:  
81 softwareupdate --all --install --force

---

<div class="post-metadata">

**Author:** ![native-api](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/native-api/32/430_2.png) [@native-api](https://travis-ci.community/u/native-api)\
**Post date:** [March 20, 2021, 6:30am UTC](https://travis-ci.community/t/mac-os-build-failing-no-error-messages-but-multiple-warnings-for-apple-old-code/11322/2 "2021-03-20T06:30:24Z")

</div>

> [@rmsharp](#):
>
> is failing with the message “No output has been received in the last 10m0s, this potentially indicates a stalled build or something wrong with the build itself.”

> **[Travis CI - Test and Deploy with Confidence](https://app.travis-ci.com/github/rmsharp/nprcgenekeepr/jobs/763492781)**
>
> Travis CI enables your team to test and ship your apps with confidence. Easily sync your projects with Travis CI and you'll be testing your code in minutes.

```auto
brew update >/dev/null

```

That’s to be expected if this command takes longer than 10 minutes.

Which it is now because the above message means that the Homebrew project lo longer provides prebuilt bottles for this OSX version so `brew` has to build them from source.  
And a very outdated preintalled Homewbrew means that `brew update` will be likely installing stuff like a new Ruby version.

---

<div class="post-metadata">

**Author:** ![native-api](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/native-api/32/430_2.png) [@native-api](https://travis-ci.community/u/native-api)\
**Post date:** [March 20, 2021, 6:43am UTC](https://travis-ci.community/t/mac-os-build-failing-no-error-messages-but-multiple-warnings-for-apple-old-code/11322/4 "2021-03-20T06:43:16Z")

</div>

@rmsharp you can skip `brew update` by specifying

```auto
disable_homebrew: true

```

in `.travis.yml`.

This can cause problems if you need to install something from Homebrew in the build.

---

<div class="post-metadata">

**Author:** ![rmsharp](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/rmsharp/32/6289_2.png) [@rmsharp](https://travis-ci.community/u/rmsharp)\
**Post date:** [March 20, 2021, 5:14pm UTC](https://travis-ci.community/t/mac-os-build-failing-no-error-messages-but-multiple-warnings-for-apple-old-code/11322/5 "2021-03-20T17:14:24Z")

</div>

> [@rmsharp](#):
>
> 10.13.

I apologize for my ignorance on this, but I do not think my .travis.yml file has anything that specifies the use of an unsupported OS (EOL). I added the “osx\_image: xcode12.2” line to the matrix section of the .travis.yml file and that has worked. Thank you again for your informative guidance.

```
matrix:
     include:
         - os: osx
           osx_image: xcode12.2
           fortran: false`

```

@jeroen Is there a something I can add to the YAML file that will not require hard coding an OSX image but will limit the tests to supported images?

---

<div class="post-metadata">

**Author:** ![native-api](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/native-api/32/430_2.png) [@native-api](https://travis-ci.community/u/native-api)\
**Post date:** [March 20, 2021, 6:12pm UTC](https://travis-ci.community/t/mac-os-build-failing-no-error-messages-but-multiple-warnings-for-apple-old-code/11322/6 "2021-03-20T18:12:39Z")

</div>

> [@rmsharp](#):
>
> I do not think my .travis.yml file has anything that specifies the use of an unsupported OS (EOL)

That’s

> [@The default \`osx\_image: xcode9.4\` is now unusable because MacOS 10.13 is EOL](https://travis-ci.community/t/the-default-osx-image-xcode9-4-is-now-unusable-because-macos-10-13-is-eol/10628):
>
> As of the release of MacOS 11.0 earlier this week, Apple and Homebrew no longer support MacOS 10.13. This means homebrew no longer provides binaries for MacOS 10.13, and on those systems, everything has to be built from source. However osx\_image: xcode9.4 is still the default os: osx image. As a result, many jobs fail because they have to start building all the brew packages from source.
