Choco install hangs forever


#1

Hi,

Thanks for the windows support!
I’m hitting a wall with a chocolatey install in this build: https://travis-ci.org/projectriff/fats/jobs/440705540#L70.


#2

Hmmmm, this is interesting because the job fails but with no extra information.

Could you try creating a branch which only does a Windows job and moving the choco install into the .travis.yml to see if anything more is displayed?


#3

Getting the same issue


#4

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:

sudo: required
language: go
go:
- '1.11'
os:
 - windows
install: true
script:
- choco install kubernetes-cli
- make -v

#5

Restarted the job, exact same result:

  • nothing for 3min8s (apart from the worker info)
  • then reaches the choco install step and stops at 3min18s

#6

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?


#7

Sadly I cannot do that as these vars are required by the stable branches as well and would impact my teammate’s work.


#8

Could you do this in a branch just for debugging?


#9

I thought the security envvars were set via Travis UI and that they affected the whole repository. Is there another way of setting them?


#10

Does choco need a -y to continue?

https://chocolatey.org/docs/commands-reference#default-options-and-switches


#11

Same thing with -y: https://travis-ci.org/projectriff/fats/builds/442249032.


#12

@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.


#13

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”.)


Go can't find GCC with go1.11.1 on Windows
#14

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 staging and trying branches.

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?


#15

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.


https://travis-ci.org/fonttools/fonttools/jobs/456966585

However, I can’t do without my secure variable.

(BTW, thanks for adding Windows support to Travis!)