Skip to content

Conversation

@LaurentGoderre
Copy link
Member

No description provided.

PeterDaveHello

This comment was marked as off-topic.

@SimenB
Copy link
Member

SimenB commented May 22, 2018

CI is unhappy, seems unrelated, though?

@chorrell
Copy link
Contributor

Yeah, looks like a problem with the npm registry:

$ npm i -g markdown-link-check
npm ERR! code E504
npm ERR! 504 Gateway Time-out: isemail@^3.1.2
npm ERR! A complete log of this run can be found in:
npm ERR!     /home/travis/.npm/_logs/2018-05-22T04_12_57_175Z-debug.log
The command "npm i -g markdown-link-check" failed and exited with 1 during .

chorrell

This comment was marked as off-topic.

@PeterDaveHello
Copy link
Member

@LaurentGoderre maybe you can rebase the branch with the latest master branch so that it'll trigger the CI build again?

I really think we docker-node members should have more permission for efficiency ...

@LaurentGoderre
Copy link
Member Author

Done!

@PeterDaveHello
Copy link
Member

CI unhappy again ... lol ...

@PeterDaveHello PeterDaveHello merged commit 3a27400 into nodejs:master May 24, 2018
@LaurentGoderre LaurentGoderre deleted the more-code-tyles branch May 24, 2018 14:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants