Don't use bootstrap on Travis #2747
Conversation
ccordoba12
commented
Oct 8, 2015
ccordoba12
commented
- The idea is not to use bootstrap to do our testing, but Spyder installed in a virtual or conda env.
- This way we will detect build and/or installation errors with Travis, as the ones I have to deal with in 2.3.5.
- The idea is **not** to use bootstrap to do our testing, but Spyder installed in a virtual or conda env. - This way we will detect building and/or installation errors with Travis, as the ones I have to deal with in 2.3.5.
|
If I am not mistaken... I was doing that originally... but somehow was removed in one of the discussions when we first implemented travis. |
|
why did you remove the test-travis flag?? |
|
Because I want to call The thing is we need to test Spyder as it's installed in Right now I'm testing building and installation manually on each release and each operating system, but I'd like Travis (and later Appveyor) to help me with that :-) |
|
By the way, this is just the first of a series of commits, but I want to test them all in Travis to see if I'm doing things correctly :-) |
This is needed by our recipe
Let's see if this pleases Travis
|
ok |
- It's needed by qtawesome
The recipe only works in Travis now
|
Ok, I think this is ready. With this work we're now building, installing and testing Spyder with the help of Besides, these changes will also help us to start testing things with @goanpeca or @blink1073, if you want to do a review, that'd be great. If not, I'll merge it tomorrow :-) |
|
👍 |
|
This is not ready yet. My changes will make all PRs with merge conflicts to fail on packaging! I'm developing a better solution now :-) |
- This will avoid the problem of having complete test failures when there are merge conflicts between the PR and master.
|
Ok, I think this is finally ready :-) |
Don't use bootstrap on Travis
