Skip to content

CI: add -v to appveyor pytest incantation #9229

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.

Sign up for GitHub

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

Jump to bottom
Closed
wants to merge 3 commits into from
Closed

CI: add -v to appveyor pytest incantation #9229

wants to merge 3 commits into from

Conversation

tacaswell
Copy link
Member

To check which test it is failing on

PR Summary

PR Checklist

  • Has Pytest style unit tests
  • Code is PEP 8 compliant
  • New features are documented, with examples if plot related
  • Documentation is sphinx and numpydoc compliant
  • Added an entry to doc/users/next_whats_new/ if major new feature (follow instructions in README.rst there)
  • Documented in doc/api/api_changes.rst if API changed in a backward-incompatible way

@anntzer
Copy link
Contributor

anntzer commented Sep 26, 2017

On a tangent, I just discovered you can remote-desktop into the appveyor VM during the build... https://www.appveyor.com/docs/how-to/rdp-to-build-worker/ handy.

@dstansby
Copy link
Member

xref #9176

@QuLogic
Copy link
Member

QuLogic commented Sep 26, 2017

-1073740791 == c0000409 == STATUS_STACK_BUFFER_OVERRUN; I've not had much luck triggering any error in valgrind on Linux, though it's a bit hard to sort through. I added pytest-faulthandler to AppVeyor here, but I'm not sure if it'll be effective.

@QuLogic
Copy link
Member

QuLogic commented Sep 27, 2017 •
edited
Loading

According to UBsan, there is a memcpy on NULL in FreeType. I am not sure if that is the cause of the problem here, but a long time ago Windows printf didn't like NULL strings so it might be the reason. (It's also triggered by a few other tests, but test_cull_markers is the first one.)

It is fixed in FreeType 2.6.3, but using that version causes 930 failures. Also, SF is not redirecting properly so we can't download it onto builders right now (it's working from cache, mostly). I'm not sure how we want to go about fixing it.

@anntzer
Copy link
Contributor

anntzer commented Sep 27, 2017

Change the download logic (setupext.py line 1181 etc.) so that on a hash mismatch the second url gets tried? Or simpler, just prefer downloading from savannah...
Although interestingly https://www.freetype.org/download.html is down too.

@QuLogic QuLogic mentioned this pull request Sep 27, 2017
Merged
2 tasks
@tacaswell
Copy link
Member Author

https://twitter.com/Slav636/status/912906308889825280 for a pointer to https://www.microsoft.com/en-us/download/confirmation.aspx?id=985 to look up details.

@QuLogic
Copy link
Member

QuLogic commented Sep 27, 2017

There's a table here for that.

@tacaswell
Copy link
Member Author

The two appevyor fails on this PR are in a different place than the rest (after all of the tests passed) or the freetype issue.

@tacaswell
Copy link
Member Author

https://ci.appveyor.com/project/matplotlib/matplotlib/build/1.0.3136
https://ci.appveyor.com/project/matplotlib/matplotlib/build/1.0.3149

@tacaswell tacaswell mentioned this pull request Oct 5, 2017
Closed
@dstansby dstansby added this to the 2.2 (next feature release) milestone Oct 8, 2017
@Kojoley Kojoley closed this Oct 14, 2017
@Kojoley Kojoley removed this from the 2.2 milestone Oct 14, 2017
@tacaswell tacaswell deleted the tst_appveyor_verbose branch October 15, 2017 03:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
topic: testing
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
5 participants
@tacaswell @anntzer @dstansby @QuLogic @Kojoley