disabling yarn gpg in Travis to fix windows hanging
was submitted in Pull Request #64 (resubmitting in #65)
as per https://travis-ci.community/t/build-doesnt-finish-after-completing-tests/288/9
Oct '18
@AviVahl
Checked it without my before_install. Still got stuck. It appears the yarn installation (and pgp verification) occurs anyway, because my repo contains a yarn.lock.
The repo is setup using yarn workspaces, so I have no proper matching alternative in npm land yet. 😦
EDIT:
tried setting env variable YARN_GPG=no (via [Travis's] configuration) to force no gpg validation, but the container appears to be stuck on: Worker information
I’ve used secure env tokens (via Travis config- “hide from log”), which seems to be broken with Windows containers. Trying regular env var to see if [the behaviour] is different.
EDIT:
Yes! It was the gpg that install.sh of yarn runs. Build now passes, after setting the YARN_GPG=no environment variable.
and as per https://travis-ci.community/t/build-doesnt-finish-after-completing-tests/288/13
Oct '18
josh (@joshk) Josh Kalderimis
Travis CI Staff (Head of Product at @travis-ci)
Hi @chrisdothtml
Could you please try adding YARN_GPG=no to your .travis.yml config to see if this helps?
@BanzaiMan do we currently detect and kill rogue processes when a build finishes?
Fixes#24
**Bug**
TSLint does `require('typescript')` to import typescript instead of taking typescript as value at runtime. Due to how node's module resolution works, this can cause TSLint to import a different typescript version than the version being used by the TS Server
This version mismatch can cause weird behavior as the ast and apis may not be compatible
**Fix**
Mock out `require('typescript')` to make sure we always return the typescript version from the server
ExE Boss
Matt Bierner
Ryan David Sheasby
Alec Larson
Qiming zhao
Benjamin Vincent
Pusztai Tibor
Bernardo
reduckted