Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Interactive backend test timeouts on wheel tests #8756

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
matthew-brett opened this issue Jun 13, 2017 · 9 comments
Closed

Interactive backend test timeouts on wheel tests #8756

matthew-brett opened this issue Jun 13, 2017 · 9 comments

Comments

@matthew-brett
Copy link
Contributor

matthew-brett commented Jun 13, 2017

I have seen a couple of timeouts for the interactive backend tests when running the wheel tests:

I suppose it may be a coincidence, but both were on Python 3.6.

EDIT: fixed links to point to job rather than log.
EDIT2: fixed links properly to point to job.

@tacaswell
Copy link
Member

links are broken 😞

@matthew-brett
Copy link
Contributor Author

I edited to point to the page for the job instead - links to logs seem to be weirdly user and browser specific.

@anntzer
Copy link
Contributor

anntzer commented Jun 13, 2017

links are still broken :(

@matthew-brett
Copy link
Contributor Author

Oops - fixed now, I believe (at least, they work for me).

@anntzer
Copy link
Contributor

anntzer commented Jun 13, 2017

Looks similar to #8679? Can you check if $DISPLAY is set (both during test collection and when the test is run)?

@matthew-brett
Copy link
Contributor Author

For reference, here is the error (same in both runs):

[gw0] darwin -- Python 3.6.0 /Users/travis/build/MacPython/matplotlib-wheels/venv/bin/python3.6
backend = 'tkagg'

    @pytest.mark.parametrize("backend", _get_testable_interactive_backends())
    def test_backend(backend):
        environ = os.environ.copy()
        environ["MPLBACKEND"] = backend
        proc = Popen([sys.executable, "-c", _test_script], env=environ)
        # Empirically, 1s is not enough on Travis.
>       assert proc.wait(timeout=5) == 0

This doesn't happen in every Python 3.6 run - it has passed a couple of times before failing again.

I think DISPLAY must be set, given the the fix to #8679.

@anntzer
Copy link
Contributor

anntzer commented Jun 13, 2017

Does explicitly unsetting $DISPLAY in .travis.yml's before_script (in the osx case) help?

@matthew-brett
Copy link
Contributor Author

@oscargus
Copy link
Member

oscargus commented Jun 1, 2022

This seems related to Travis which is no longer used. If the same problem exists on other CIs, feel free to reopen.

@oscargus oscargus closed this as completed Jun 1, 2022
@QuLogic QuLogic closed this as not planned Won't fix, can't repro, duplicate, stale Jun 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants