I just set up a minimum example: https://travis-ci.org/projectriff/fats/jobs/441544279.
Nothing happens for about 3 minutes and then it fails all of a sudden (apart from the worker information display).
I reduced the
.travis.yml file to the minimum version:
- choco install kubernetes-cli
- make -v
Restarted the job, exact same result:
- nothing for 3min8s (apart from the worker info)
- then reaches the choco install step and stops at 3min18s
Are you using any secure environment variables in your build? There is a known issue where this can block the streaming output. We are working to address this, but in the mean time can you try removing the secure env vars and see if this helps?
Sadly I cannot do that as these vars are required by the stable branches as well and would impact my teammate’s work.
Could you do this in a branch just for debugging?
I thought the security envvars were set via Travis UI and that they affected the whole repository. Is there another way of setting them?
@fbiville ah yes, you are right, secure env vars from settings!
I will see if I can test for this issue over the next couple of days.
Otherwise, if you have time, you could create a dummy open source project for testing.
Sorry for the delay, I’m at GitHub Universe this week.
I can confirm that this is a manifestation of the secrets issue: https://staging.travis-ci.com/BanzaiMan/fats/builds/233444 has no secrets and runs to completion. (If this URL does not work, please try going to https://staging.travis-ci.com/BanzaiMan/fats/requests and clicking on “Build #1”.)
Trying to set up the Windows build for rust-clippy, we managed to get the Pull Request builds to pass.
However, when we are using bors to approve the PR, the windows build fails without any errors when running
choco install windows-sdk-10.0 -yv.
The same command is executed in a PR build without problems. This only seems to happen on the
Failing build log on
trying branch: https://travis-ci.org/rust-lang-nursery/rust-clippy/jobs/453515506#L67
Successful build log from the PR: https://travis-ci.org/rust-lang-nursery/rust-clippy/jobs/453509285#L81
We do use secrets in our Travis CI config, so this may be related. Is there anything we can do to work around this issue?
I’m having the same issue with
choco install python3 command seemingly hanging forever until the build finishes with a failure, but no error message is printed.
If I comment out my secure variable (which i use to upload package to PyPI using twine), then it works.
However, I can’t do without my secure variable.
(BTW, thanks for adding Windows support to Travis!)
@josh Sorry for the ping, are there any news regarding a potential fix or workaround when using environment secrets?
@phansch Depending on the use case, it may be possible to separate the secure vars from choco install using matrix.
+1 for a better way to do this though
Hi @josh, is there any update on this issue? Had assumed this was now fixed since we are seeing
choco install consistently work fine in a Windows job we recently added on travis-ci.org (e.g. https://travis-ci.org/projectriff/riff/jobs/468099790) but, in an almost identical Windows job set up on travis-ci.com, the
choco install repeatedly hangs as previously reported.
choco install work on travis-ci.org but hang on travis-ci.com?
Hi @josh, is there any news on when
choco install will work?
I’m also affected by this issue here: https://travis-ci.org/libretro/snes9x/jobs/476393331
Using an encrypted private key.
I can confirm that there is an incompatibility between secret env vars and choco.
Deleting my secret env vars (related to an SSH key) fixed choco.
You can see the difference between this build https://travis-ci.org/libretro/snes9x/jobs/478221767
And this one https://travis-ci.org/libretro/snes9x/builds/478222865?utm_source=github_status&utm_medium=notification
/c/Users/travis/.travis/job_stages: line 692: /c/Users/travis/.ssh/config: No such file or directory error that appears only when secret env vars are used with choco.
filter_secrets: false fixed it for me