Stuck on an issue?
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.
Slow `building environment` state
See original GitHub issueHow fast docker should run building environment state?
For me on MacBook air 2015 (8gb ram) with one container (node 7.4.0) it takes 1:50 min, it looks very slow. Docker takes 2 gb ram and 2 core.
With 5 containers time about 17 min.
sudo: false
language: node_js
node_js:
- "4.3.0"
- "4"
- "5"
- "6"
- "stable"
cache:
yarn: true
directories:
- node_modules
script: "yarn run travis"
after_success:
- yarn run test:coveralls
- rm -rf ./coverage
Issue Analytics
- State:
- Created 7 years ago
- Reactions:1
- Comments:10 (2 by maintainers)
Top Results From Across the Web
The Slow Building Movement - Shelterforce
The “slow building” movement focuses on creating designs that are appropriate for a given bioregion, taking into account climate, natural ...
Read more >Accelerating green growth in built environment | McKinsey
Creating green growth requires shifts in how players design, build, operate, and decommission assets.
Read more >Slow Space - Slow Food for the Built Environment
Slow Space is Slow Food for the built environment. It is a philosophy, a movement and a way of life that promotes meaning...
Read more >Changes in building and construction have great potential to ...
A design with fewer or alternative materials, and more recycling of construction materials are among the most promising strategies, it says.
Read more >The Slow Bake of Our Infrastructure - Scientific American
As the climate warms, heat waves have become longer, more frequent and more deadly, at their worst killing thousands of people.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
You could point npm cache to your host machine? This problem usually exists if there is no shared cache, in the case of docker the cache should be stored outside the container
@vadimdemedes Can you try running
trevorin the Got repository?