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.
dependency resolution fails on travis ci and within docker containers
See original GitHub issueSee https://travis-ci.org/holgerbrandl/kscript
It seems related to the stream-redirection settings used in runProcess()
Issue Analytics
- State:
- Created 6 years ago
- Comments:5
Top Results From Across the Web
Common Build Problems - Travis CI Docs
One possible cause for builds failing unexpectedly can be calling set -e (also known as set errexit ), either directly in your .travis.yml...
Read more >Docker in TravisCI causes linking db's to fail #4842 - GitHub
The linking is done properly, because the etc/hosts has records of db and the ENV variables are all properly set, because of the...
Read more >Is there a way to get information about a failed deploy on ...
i am working around docker and try to push a docker repository via GitHub & Travis-ci. My push doesn't work and i don't...
Read more >Leaving travis for docker – will I get my life back? - General
I understand that this is, in some way, inevitable to ensure reproducibility: the failed Travis build indicated that I was relying on some...
Read more >Building A CI/CD Pipeline With Travis CI, Docker, And ...
With the help of well-designed Continuous Integration systems in place, teams can build quality software by developing and verifying it in ...
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
Thanks for input again. Fixed in today’s v2.2 release.
Indeed, hitting the piped stream’s capacity limit seems the most reasonable explanation. I’m working on a fix now. Luckily that fix will also solve #23 which is pretty related to this ticket and easy to fix once we have better control over the spawned process out/err streams.