tests: temporarily pin pytest to fix AppVeyor builds

[benoit-pierre]

No description provided.

[benoit-pierre]

Can this be merged? I have a workaround for not hitting the limit even with pytest>3.8.2, but it's rather more involved.

[cjerdonek]

Can you add a trivial news entry so a green checkmark will be visible for this commit?

[benoit-pierre]

Or you could add the trivial label :P

[cjerdonek]

Oh, I didn't know about that feature. :)

[pradyunsg]

It's noted in the docs for news entries.

Which reminds me, @cjerdonek have you been added to the other platforms like RTD? There's a list in the dev docs.

[cjerdonek]

It's noted in the docs for news entries.

Yes, I see that now. Part of my surprise was that the label can be added even after tests are run, and it will go back and change the test result. I was thinking it needed to be added beforehand. (I also now know that you can trigger tests to be re-run by closing and re-opening the issue.)

[cjerdonek]

have you been added to the other platforms like RTD?

I don't think so. Something else I don't see on that list is reference to the PyPA-Committers mailing list.

[cjerdonek]

I have a workaround for not hitting the limit even with pytest>3.8.2, but it's rather more involved.

I wonder if pytest could expose or change something to make it easier to work around this issue..

[pradyunsg]

@cjerdonek We should smoothen our "on-boarding process" for new committers but then again, it doesn't really happen often enough.

If there's any improvement in language to that text that would have helped you, a PR would be nice. :)

IIRC, @dstufft is the right person to put up a mail to, for adding you to pypa-committers. It's really a temporary measure for figuring out some things over the short term so I don't want to get that documented. I'll come around to adding you on the documented platforms myself, before the Bloomberg Sprint happens otherwise during it.

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.