You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In one of my playbook's builds on Travis CI, I started getting build errors due to timeouts:
TASK [elliotweiser.osx-command-line-tools : Install Command Line Tools] ********
No output has been received in the last 10m0s, this potentially indicates a stalled build or something wrong with the build itself.
903Check the details on how to adjust your build configuration on: https://docs.travis-ci.com/user/common-build-problems/#Build-times-out-because-no-output-was-received
This only happens in the xcode11.4 Travis CI build environment (10.15), and doesn't seem to happen on the 10.14 environment.
Could this be a Travis CI misconfiguration, or could it really be taking that long?
The text was updated successfully, but these errors were encountered:
Sometimes it just takes that long. We're at the mercy of the softwareupdate servers.
Considering that the command line tools should already be installed on the Travis CI OS X images, there should be no need to go through these steps. It looks like one of the idempotence checks is failing:
TASK [elliotweiser.osx-command-line-tools : Check the Command Line Tools package metadata] ***
fatal: [localhost]: FAILED! => {"changed": false, "cmd": ["pkgutil", "--pkg-info=com.apple.pkg.CLTools_Executables"], "delta": "0:00:00.265464", "end": "2020-06-15 16:06:32.697657", "msg": "non-zero return code", "rc": 1, "start": "2020-06-15 16:06:32.432193", "stderr": "No receipt for 'com.apple.pkg.CLTools_Executables' found at '/'.", "stderr_lines": ["No receipt for 'com.apple.pkg.CLTools_Executables' found at '/'."], "stdout": "", "stdout_lines": []}
...ignoring
In one of my playbook's builds on Travis CI, I started getting build errors due to timeouts:
This only happens in the
xcode11.4
Travis CI build environment (10.15), and doesn't seem to happen on the 10.14 environment.Could this be a Travis CI misconfiguration, or could it really be taking that long?
The text was updated successfully, but these errors were encountered: