pytest not found error

Davis King's Avatar

Davis King

11 Nov, 2018 03:17 PM

I recently started getting failed builds due to pytest not being found. Nothing has changed, and this only happens on my python 3.5 tests.
 The other versions of python (e.g. 2.7, 3.6, 3.7) work fine. An example of a failed test is: https://ci.appveyor.com/project/davisking/dlib-1mqn9/builds/20177058/job/ah3iuh4hgg9c1la7

Note that pytest gets installed, according to the logs. But the test ends up failing with the error `The 'pytest' distribution was not found and is required by the application`. I've restarted the test a few times but the issue persists.

  1. Support Staff 1 Posted by Owen McDonnell on 13 Nov, 2018 05:14 PM

    Owen McDonnell's Avatar

    I see that the version of pytest changed between your successful builds and failing builds. As a test, can you specify the older/last working version (looks like 3.8.1) and try to build.

  2. 2 Posted by Davis King on 14 Nov, 2018 12:28 PM

    Davis King's Avatar

    Trying 3.8 now. However, 3.10.1 works for every other version of python.
    It doesn't really make any sense to me that it only fails for Python 3.5 on
    Windows.

  3. Support Staff 3 Posted by Owen McDonnell on 15 Nov, 2018 12:48 AM

    Owen McDonnell's Avatar

    Nor to me, but do you think it is specifically an AppVeyor problem?

  4. 4 Posted by Davis King on 17 Nov, 2018 02:30 AM

    Davis King's Avatar

    I'm not sure. I haven't tried that specific version of python on windows
    with that version of pytest. Maybe it's a pytest bug. That's certainly
    possible.

Reply to this discussion

Internal reply

Formatting help / Preview (switch to plain text) No formatting (switch to Markdown)

Attaching KB article:

»

Attached Files

You can attach files up to 10MB

If you don't have an account yet, we need to confirm you're human and not a machine trying to post spam.

Keyboard shortcuts

Generic

? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac