Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Cache restore slow compared to Semaphore CI
See original GitHub issueSemaphore CI have a cache similar to actions/cache@v1 but theirs only takes six seconds to restore our 760MB node_modules Semaphore CI, compared to twenty eight seconds on GitHub Actions.
This was on Semaphore’s lowest machine type which is comparable to the specifications of the GitHub-hosted runners.
This behavior was observed on multiple builds across several days.
I don’t have a repro because this was observed on a private repo, but it’s easy enough to replicate. I’ll create one if it’s deemed necessary?
Issue Analytics
- State:
- Created 4 years ago
- Comments:12 (9 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Could you try to use the v2?
We’re already working on making it faster, and in my environment it’s about three times faster. The next major version will definitely improve.