-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Test suite failing on Node.js v14.6.0 #128
Comments
|
shot has been re-enabled on citgm
…On Tue, Jul 21, 2020 at 10:57 PM Colin Ihrig ***@***.***> wrote:
@***@***.*** was published with ***@***.***
<hapijs/lab@0a5adf0>.
The shot CI is now passing
<https://travis-ci.org/github/hapijs/shot/jobs/710214180> on Node v14.6.0.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#128 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AADZYVZLFQD5DN6NQPURKODR4ZIS3ANCNFSM4PDXIBRQ>
.
|
Hey @cjihrig shot is still failing in CI because the lab update hasn't landed in a release (at least that is my assumption). Are you planning a release soon or should we remove shot from CITGM for the time being? |
Any chance you're running into caching issues? The lab change was published as 22.0.5, and shot relies on 22.x.x. Can you verify that CITGM is testing against lab 22.0.5? |
Unsure if it is a caching thing... I just reproduced locally with I was also able to reproduce in a clone of the shot repository with a fresh npm install |
I did a fresh clone with a fresh npm install, and it worked fine for me. Can you run
|
I flushed my cache and removed a local package-lock.json and managed to get
it working... so indeed it sounds like a caching issue in CITGM.
…On Tue, Jul 28, 2020 at 6:04 PM Colin Ihrig ***@***.***> wrote:
npx citgm -v verbose shot doesn't work for me locally. I get this warning:
primordials is not defined
Warn |update-available |v7.1.1 (current: v0.1.0)
| |npm install -g citgm
I was also able to reproduce in a clone of the shot repository with a
fresh npm install
I did a fresh clone with a fresh npm install, and it worked fine for me.
Can you run npm ls @hapi/lab:
$ npm ls @hapi/lab
@***@***.*** /private/tmp/shot
└── @***@***.***
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#128 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AADZYV4BZT2C6P6PPCN6LWDR55DQHANCNFSM4PDXIBRQ>
.
|
Cool. FWIW, we are due to publish a new major version of |
This is due to new global variables that are unknown to lab
I've opened a PR to fix this -> hapijs/lab#981
Until this is fixed we are skipping shot on v14.x in CITGM nodejs/citgm#813
Once the upstream lab fix has landed and shot has been fixed we can revert that change on CITGM
The text was updated successfully, but these errors were encountered: