Adjustments to cleanup travis CI

[mmcky]

1. Use a full anaconda environment to have the same environment as users. This might slow down the setup phase - and if so we can restore to a minimal environment.

[mmcky]

Trying to remove any dependency on sudo so that we can leverage the faster containerized travis builds.

@spencerlyon2 or @cc7768: Do you recall what these lines were for in the setup phase of travis?

  - sudo rm -rf /dev/shm
  - sudo ln -s /run/shm /dev/shm
``

[sglyon]

Nope, those don't look familiar to me.

// Spencer
On Feb 24, 2016 18:10, "mmcky" [email protected] wrote:

Trying to remove any dependency on sudo so that we can leverage the
faster containerized travis builds.

@spencerlyon2 https://github.com/spencerlyon2 or @cc7768
https://github.com/cc7768: Do you recall what these lines were for in
the setup phase of travis?

• sudo rm -rf /dev/shm
• sudo ln -s /run/shm /dev/shm``

—
Reply to this email directly or view it on GitHub
#230 (comment)
.

[mmcky]

Looks like a way to speed up things by holding objects in RAM. I am going to remove them from our test configuration as they require sudo to execute and we should migrate to the new container service. The easy way to do that is specify sudo: false.

http://askubuntu.com/questions/169495/what-are-run-lock-and-run-shm-used-for