Skip to content
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

Include missing conftest.py #1358

Closed
wants to merge 1 commit into from
Closed

Conversation

ghisvail
Copy link
Contributor

@ghisvail ghisvail commented Apr 7, 2017

The tests cannot be run from the release tarball without this file.

The tests cannot be run from the release tarball without this file.
@ghisvail
Copy link
Contributor Author

ghisvail commented Apr 7, 2017

Unfortunately, even if I patch the code base to add the missing file, the tests cannot be run due to the following bug: pytest-dev/pytest#1889

Too bad you guys decided to change the design of the test suite for a point release :-(

@shoyer
Copy link
Member

shoyer commented Apr 8, 2017

This is embarrassing -- thanks for the catch.

conftest.py seems to be much more troublesome than the pytest documentation suggests. Another alternative is to make the test-suite robust to its absence, and not bother to packaging it, given that it is mostly useful for development purposes.

@shoyer shoyer added this to the v0.9.3 milestone Apr 8, 2017
@ghisvail
Copy link
Contributor Author

ghisvail commented Apr 8, 2017

Another alternative is to make the test-suite robust to its absence, and not bother to packaging it, given that it is mostly useful for development purposes.

If by packaging you mean distributing here, then I am very disappointed by your statement. From a package maintainer's perspective, I would consider the lack of a test suite a severe regression, should the latter be removed from source distribution in the future.

I would also remind you that it is that very same test suite that lead to the triage of the regressions with bottleneck whilst I was bootstrapping the Debian packaging effort.

Please consider fixing the current test suite or reverting to the old design. The fact that conftest.py does not work reliably (see the bug linked above) should be a sign that the decision to jump to this design happened too soon.

@shoyer
Copy link
Member

shoyer commented Apr 8, 2017

If by packaging you mean distributing here, then I am very disappointed by your statement. From a package maintainer's perspective, I would consider the lack of a test suite a severe regression, should the latter be removed from source distribution in the future.

I agree. I meant not distributing conftests.py in the pypi package (and making the test suite run without it), not removing the test suite.

@ghisvail
Copy link
Contributor Author

ghisvail commented Apr 8, 2017

There is a special note for pytest_addoption which might explain the problem.

@ghisvail
Copy link
Contributor Author

ghisvail commented Apr 8, 2017

I can get the tests to work at build time, but the CI tests using --pyargs (to test against the installed library under site-packages) no longer do, i.e. I get a bunch of ValueError: no option named '--run-flaky'

@ghisvail
Copy link
Contributor Author

ghisvail commented Apr 8, 2017

I can get the tests to work at build time

By adding conftest.py manually if that was not clear.

@ghisvail
Copy link
Contributor Author

ghisvail commented Apr 8, 2017

And it looks like most projects in the Debian archive using pytest_addoption have it declared either as a plugin or inside the tests folder, as the note in the pytest documentation says.

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

Successfully merging this pull request may close these issues.

2 participants