Closed kain88-de closed 9 years ago
I thought container builds are the default nowadays, and you'd only get something different with sudo: True
.
I got a message about using the old infrastructure on the travis build. The docs say that they are only explicitly activated with the sudo flag
Hi Max,
I got a message about using the old infrastructure on the travis build. The docs say that they are only explicitly activated with the sudo flag
Then I obviously mis-remembered. I thought that MDAnalysis runs on the new containers even though the sudo=false is flag is not set. At least that's what I remember from conversations with @richardjgowers and checking the log such as https://travis-ci.org/MDAnalysis/mdanalysis/builds/80046564 says that it is using docker and containers:
Using worker: worker-linux-docker-bf8ff456.prod.travis-ci.org:travis-linux-3
This job is running on container-based infrastructure, which does not allow use of 'sudo', setuid and setguid executables. If you require sudo, add 'sudo: required' to your .travis.yml See http://docs.travis-ci.com/user/workers/container-based-infrastructure/ for details.
Cheers, Oliver
@orbeckst you're not wrong, MDAnalysis defaulted to container based once we got rid of sudo. I'm not sure why this didn't too, but it's fixed now
lets see if this works