Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Appveyor: use newer conda packages and only run all tests on one platform #6774

Merged
merged 4 commits into from Jul 18, 2016

Conversation

jankatins
Copy link
Contributor

@jankatins jankatins commented Jul 17, 2016

Since setting the miktex version as a workaround for the miktex related build failures, the miktex package was updated and an inkscape package was added in conda-forge.

Also install these packages only on one build so that the rest of the builds are shorter...

Also includes the enablement of the conda packages again.

Closes: #6682

@jankatins
Copy link
Contributor Author

So, this passes on appveyor and now runs the latex (and other) tests in the Py27/32bit build. This is the first build and takes 30min vs the rest which take 7-8 mins. I'm wondering if putting the full tests in the second run would make more sense so that the first run is fast and one can iterate based on the results of that run (assuming that in most cases changes will only touch non-latex codapaths).

Comments?

@tacaswell
Copy link
Member

Most of the time when I am waiting on appveyor it is due to there being many jobs stacked up, but re-ordering them to put a fast one first sounds like a good idea.

@jankatins
Copy link
Contributor Author

And it works... Please have a look and merge if satisfied...

@jenshnielsen jenshnielsen merged commit e3fd1b1 into matplotlib:master Jul 18, 2016
@QuLogic QuLogic added this to the 2.1 (next point release) milestone Jul 18, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants