travis unix linux builds can't find gcc sometimes
See original GitHub issueDescribe the bug Travis linux builds seem to fail occasionally. The culprit seems to be packages that need gcc to install cannot find gcc.
unable to execute ‘gcc’: No such file or directory error: command ‘gcc’ failed with exit status 1
How to reproduce
Run code through Travis CI tests
Expected behavior
if local tests pass, they should pass on Travis, but often they fail.
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
travis unix linux builds can't find gcc sometimes #266 - GitHub
Travis linux builds seem to fail occasionally. The culprit seems to be packages that need gcc to install cannot find gcc.
Read more >Why is Travis CI's xenial VM finding gcc 5 and 7, but not 6?
The reason this happens is that GCC 6 is Ubuntu Xenial's distribution's default version. So it's not available as a versioned-name binary, ...
Read more >Installing Dependencies - Travis CI Docs
If you want to update apt-get update automatically on every build, there are two ways to do ... For example, to install gcc...
Read more >Travis build failure - Page 4 - FreeCAD Forum
P.S. I noticed Windows builds can sometimes get closely to 2 hrs 30 min limit. ... I worry a bit, as GCC builds...
Read more >Continuos Integration on Linux and Windows: Travis and ...
Let's see how to use Travis and AppVeyor to ensure your code works on Linux and Windows. See the exact steps to get...
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 FreeTop 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
Top GitHub Comments
https://github.com/psf/black/issues/1112 👀
This seems to happen in particular with the linux python 3.7 tests.
That one uses
dist: xenial
so I tried removing it to see if that helped. It did not help.