You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I put forward a pull request but it seems that it's very hard to pass the test of Travis CI. >_<
My PR's link is #515. The Travis CI always tell me when installing some NPM packages such like secp256k1, the npm got a 404 error and the test failed immediately. But all tests run well on my own computer, so I wonder that what happend in Travis CI?
The text was updated successfully, but these errors were encountered:
vita-dounai
changed the title
Travis CI get stuck in "npm ERR! code E404"
Travis CI got stuck in "npm ERR! code E404"
Aug 6, 2019
@vita-dounai @nklincoln is looking into this issue, which is also affecting the other PRs. Current guess is, that it's a resource limitation from the Travis side.
I put forward a pull request but it seems that it's very hard to pass the test of Travis CI. >_<
My PR's link is #515. The Travis CI always tell me when installing some NPM packages such like
secp256k1
, the npm got a 404 error and the test failed immediately. But all tests run well on my own computer, so I wonder that what happend in Travis CI?The text was updated successfully, but these errors were encountered: