Windows VM not booting

[bdejong]

Hey,

got a rather “trivial” YAML up and the windows version has been “Waiting to start” for two hours now…

Is the windows pipeline down, or am I doing something wrong?

language: generic

git:
  depth: 1

os:
- osx
- windows

before_script:
- git submodule update --init --recursive
- cd holoplotApp/Source/UnitTests
- if [[ "$TRAVIS_OS_NAME" == "osx" ]];
  then cmake .;
  else cmake -G "Visual Studio 15 2017 Win64" .;
  fi
- cd -

script:
- if [[ "$TRAVIS_OS_NAME" == "osx" ]];
  then xcodebuild -project holoplotApp/Builds/MacOSX/holoplotApp.xcodeproj;
  else msbuild holoplotApp/Builds/VisualStudio2017/holoplotApp.sln;
  fi
- cd holoplotApp/Source/UnitTests
- if [[ "$TRAVIS_OS_NAME" == "osx" ]];
  then make;
  else msbuild UnitTests.sln;
  fi
- cd -

after_success:
- cd holoplotApp/Source/UnitTests
- if [[ "$TRAVIS_OS_NAME" == "osx" ]];
  then ./unittests;
  else Release/unittests.exe;
  fi

# Disabled notifications for now as they stop the windows builds to appear...
# notifications:
#   slack:
#     secure: YSrF32REBSrbuhdMmZph[snip]I8aIPVQ=
#     on_success: change
#     on_failure: change

Bram

[native-api]

Same here, even if I delete everything except language: and os:. Windows VMs seem to be broken.

[bdejong]

Ah, good to know it’s not me!
Anyone here currently getting successful windows boots?

[BanzaiMan]

Secure environment variables are known to cause problems; it is one of the issues listed in the Known issues post.

Current known issues — Please read this before posting a new topic

Here are some issues that we know about, beyond language support. VM fails to come up if you have secrets This happens whether they are in Settings, or encrypted in .travis.yml. Caching is not yet supported This is now working in production on both .com and .org. Debug mode is not supported NVS version names are different from those of NVM As a result, some names in nvm do not work on Windows, and names on nvs do not work on Linux and macOS. Compare nvm names (via nvm install) and nvs n…

If your builds do not have secrets, please indicate the build log URLs so we can look at them.

[bdejong]

There are no secrets in the travis script.
There is never a build log and it just gets stuck at “Waiting to start”.
One I left for 2 hours, one for 6 hours.

I just triggered this one: https://travis-ci.com/holoplot/msg_beta/jobs/161120594
So you can see for yourself…

[BanzaiMan]

Hmm. The image selection is wrong. Could you switch language: generic to language: bash? (Please cancel the current job, too.)

[bdejong]

Will try this first thing tomorrow…

Bram

[bdejong]

Yep! This does the trick!

I’m getting further along…

Bram

[Lekensteyn]

This issue still exists, my .travis.yml file contained language: minimal and VMs would never start. Changing it to language: c (in the matrix) allowed the VM to boot.