-
Notifications
You must be signed in to change notification settings - Fork 150
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
lib: introduce a timeout to npm test
#441
Conversation
My first code contribution to CITGM for your reviewing pleasure. Should this be addition be documented? |
Do you CI on Jenkins? |
Ack. |
Delinted. |
CI looks good (almost perfect), PTAL |
Ping: timeouts are a PITA (they clog the CI 😞) https://ci.nodejs.org/job/citgm-smoker/nodes=osx1010/897/ Rerun CITGM CI: https://ci.nodejs.org/view/Node.js-citgm/job/citgm-continuous-integration/30/ |
Is it's just me or is the CI actually red (with |
@refack yep, CI is red on master |
When did this happen? Is there pr that broke it or is it just a platform
regression?
…On Jul 6, 2017 1:13 PM, "Gibson Fahnestock" ***@***.***> wrote:
@refack <https://github.com/refack> yep, CI is red on master
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#441 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAecVweSFRHd-4GrcSSIu9YEUvrbg6qWks5sLMFBgaJpZM4N48I9>
.
|
Anyone with a mac can reproduce? |
This may be due to new osx maxhines in ci. I can check in a short bit
…On Jul 6, 2017 1:57 PM, "Michaël Zasso" ***@***.***> wrote:
Anyone with a mac can reproduce?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#441 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAecV-0ObeoqNVsMsiMYj0sxSHUgnvQFks5sLMu1gaJpZM4N48I9>
.
|
It's red across the board: AFAICT it's an |
Oh sorry, I looked at the results from an earlier run (the 4 failing checks that GitHub shows) |
npm 5 broke the tests. Fix: #447 |
Fix landed, can you rebase and re run CI please
…On Thu, Jul 6, 2017 at 4:01 PM, Michaël Zasso ***@***.***> wrote:
npm 5 broke the tests. Fix: #447
<#447>
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#441 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAecV-5i2SzuPK_y_D4I0fUFXMyV-Y21ks5sLOirgaJpZM4N48I9>
.
|
@refack can you look into why travis is failing? |
yup
It is failing with a timeout, which made me think it might be relevant
… On Jul 10, 2017, at 11:47 AM, Refael Ackermann ***@***.***> wrote:
Just making sure, that variation is node 6 on macOS?
<https://user-images.githubusercontent.com/96947/28014696-a871f714-653b-11e7-99a8-0e69af5c63fb.png>
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub <#441 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAecV-5qwuEVlrJEsKLrl7v8JRH3NAJWks5sMgFSgaJpZM4N48I9>.
|
landed in 77b1cd6 release in 2.0.6 If there are issues we can revisit |
Ohh, I'll recheck 6/macOS |
Fixes: #426
Checklist
npm test
passes