Skip to content

Make CI fail if interactive toolkits can't be tested #11497

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

Closed
wants to merge 3 commits into from

Conversation

anntzer
Copy link
Contributor

@anntzer anntzer commented Jun 24, 2018

PyQt5.11 appears to break the build (I can reproduce the failure
locally).

Also make it a failure to fail to install the GUI toolkits for testing,
to avoid missing new failures there.

Also supersedes #11494.

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

.travis.yml Outdated
python -mpip install --upgrade $PRE pgi
python -c 'import pgi as gi; gi.require_version("Gtk", "3.0"); from pgi.repository import Gtk'
fi
python -c 'import PyQt5.QtCore'
Copy link
Member

Choose a reason for hiding this comment

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

These still need the echo bit to make sure the build doesn't fail if they aren't importable.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Actually the point is exactly to fail when they are not importable, instead of having to figure this out manually every time this happens.

@QuLogic
Copy link
Member

QuLogic commented Jun 24, 2018

I have a hack solution to fix PyQt5 5.11 here, but I need to turn it into something reasonable.

@QuLogic
Copy link
Member

QuLogic commented Jun 24, 2018

See #11500.

@anntzer
Copy link
Contributor Author

anntzer commented Jun 24, 2018

PyQt5.11 has been withdrawn (https://riverbankcomputing.com/pipermail/pyqt/2018-June/040459.html), so I repurposed the PR to just move GUI deps to requirement files too and fail the CI when they fail to install properly.

@anntzer
Copy link
Contributor Author

anntzer commented Jun 25, 2018

So it appears that the interactive tests are failing with wx+OSX. Any OSX specialist wants to have a look at this (can you repro locally?), or should we just skip them?

@tacaswell tacaswell added this to the v3.0 milestone Jul 1, 2018
@jklymak
Copy link
Member

jklymak commented Jul 3, 2018

I'm a little confused where we stand here. Right now none of the Travis CI tests are passing because of QT5 issues. Is this fix, correct, or #11500? or are they complimentary?

@anntzer anntzer changed the title Pin PyQt5 to <5.10. Make CI fail if interactive toolkits can't be tested Jul 3, 2018
@anntzer
Copy link
Contributor Author

anntzer commented Jul 3, 2018

See #11500 (comment); as for this PR the scope has changed and I renamed it accordingly.

# pgi is only installable on Linux
pyqt5
# wxpython 4.0.2 is broken on OSX, see https://groups.google.com/forum/#!topic/wxpython-dev/lNvdniiXhdY
wxpython!=4.0.2
Copy link
Member

Choose a reason for hiding this comment

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

Looks like 4.0.3 is also failing now?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

let's try excluding it too...

Copy link
Member

Choose a reason for hiding this comment

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

Fails to build faster! Actually I'm not clear why the mac build is trying to use 3.7....

Also make it a failure to fail to install the GUI toolkits for testing,
to avoid missing new failures there.
@jklymak
Copy link
Member

jklymak commented Jul 4, 2018

Force-pushed a change to pin python to 3.6 for OS X. It was trying to use 3.7.

@jklymak
Copy link
Member

jklymak commented Jul 5, 2018

Well, that didn't work either. Sorry, you should revert my commits...

@anntzer
Copy link
Contributor Author

anntzer commented Jul 5, 2018

but now it's failing on something different (pyqt5). I'll try something later.

@jklymak
Copy link
Member

jklymak commented Feb 9, 2019

This looks to be broken, but feel free to re-open if I'm wrong...

@jklymak jklymak closed this Feb 9, 2019
@anntzer
Copy link
Contributor Author

anntzer commented Feb 11, 2019

I think some variant of this PR should still go in, but let's do this after the current qt breakage is fixed :)

@anntzer anntzer deleted the pinpyqt branch February 11, 2019 06:35
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.

5 participants