Closed osumampouw closed 8 years ago
@a-murphy can you take a look?
It looks like this was occurring at the same time that we were having a problem caching (https://github.com/Shippable/support/issues/2664), and your builds started failing when the cache wasn't available. The last successful build was the last one to use the cache. It's quite likely that npm install
installed a different version of something without the cache.
@osumampouw With the "problem caching" issue resolved, you should have healthy builds now. Do let us know if it is otherwise.
Description of your issue:
Here's my project: https://app.shippable.com/projects/552c7ec75ab6cc1352c300d8
Starting from this build https://app.shippable.com/runs/574c3733e77e550d00fadf81 Our build script always failed to build.
This is the last healthy build https://app.shippable.com/runs/574be82c8d819e0d00ab8d97
When we revert the failing build, shippable is still failing to build the reverted commit. We also tried running the build on our local machine and it worked. Then we also tried rebuilding the last healthy build, and that also fail to build. So we decided to clear the build cache and retry again, but that also failed. So from the experiments above, we concluded there's something wrong with shippable build. Can you help investigate?