Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions .travis.yml
Original file line number Diff line number Diff line change
Expand Up @@ -77,6 +77,10 @@ before_install:
- pushd builds
# Build into own virtualenv
# We therefore control our own environment, avoid travis' numpy
#
# Some change in virtualenv 14.0.5 caused `test_f2py` to fail. So, we have
# pinned `virtualenv` to the last known working version to avoid this failure.
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How does this comment look to you?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks OK.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would be good to figure out why it fails, but I don't have time today and
it doesn't sound like anyone else does, so oh well a temporary hack does
put off the problem :-)
.
(Adding an 'ls path/to/venv/bin' to a failing build would be informative
about what's going on...)
.
NB for clarity: "virtualenv" and "venv" are actually two different things
(venv's are virtualenv-like environments that are provided as a built-in
feature of recent py3 releases).

On Fri, Feb 5, 2016 at 12:42 PM, jakirkham [email protected] wrote:

In .travis.yml
#7197 (comment):

@@ -77,6 +77,10 @@ before_install:

  • pushd builds

    Build into own virtualenv

    We therefore control our own environment, avoid travis' numpy

    • Some change in virtualenv 14.0.5 caused test_f2py to fail. So, we have

    • pinned virtualenv to the last known working version to avoid this failure.

How does this comment look to you?


Reply to this email directly or view it on GitHub
https://github.com/numpy/numpy/pull/7197/files#r52070007.

Nathaniel J. Smith -- https://vorpus.org http://vorpus.org

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Haha, yeah, would be nice. Figured I'd just end the stream of Travis failed emails instead.

Honestly, it is cases like this where I start preferring a different sort of CI all together like CircleCI where one can inspect the VM or Wercker where one can not only inspect a failed build, but can run the CI locally. The hack stuff into the CI script and wait a few minutes before more hacking just doesn't cut it for me.

Yep, I did discover that recently. Still this somehow fixes it. Kind of a mystery why atm.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, the problem is that AFAICT Travis is more generous than everyone else with respect to how much CPU time they offer to open source projects (e.g. CircleCI gives you 3 parallel workers, Drone.io gives you 1, Travis gives you 6. OTOH I haven't checked how fast Travis's workers are compared to the others...).

I'm 95% sure I saw somewhere where you can download the Travis container images to run locally, but now I can't seem to find it :-(

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, I thought I saw some sort of Travis CLI tool at some point too, but the docs on this seem to disappear, as well.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I suppose there is this ( https://github.com/travis-ci/travis-build ) and this ( https://github.com/travis-ci/worker ), but it feels like a bit much to get started with.

Alternatively, there is a docker image ( https://github.com/SonarSource/local-travis ) that can be pulled from Docker Hub that might be more friendly, but this is unofficial.

- pip install -U 'virtualenv==14.0.4'
- virtualenv --python=python venv
- source venv/bin/activate
- python -V
Expand Down