-
Notifications
You must be signed in to change notification settings - Fork 23
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
Tests dir is missing files in sdist/pip tarballs #27
Comments
These are caused by various files missing from the tests subdir in the ports package. What did you use to make the ports package file list? Did that come from MANIFEST.in? |
The |
Can you tell me the exact commands you ran to get to this test failure, including build and install commands? I did a --record on an install and I think that might be a different thing. It does not list any test files. |
(Note I do not have FreeBSD so I can't do the ports thing.. but this is not a FreeBSD-specific issue.. it is an issue with however the list of files was generated in the port tree). |
IMO, you should publish how to run testcases. Please keep in mind that it should run testcases without the package being installed. |
I run test cases in 'tox', which sets up virtualenvs for python3, python2.7, and pypy and runs the test cases in their own isolated environment, after building pip packages for them. This is why I am confused and wondering how you built the package and got the file list. The tox system should be building standard pip bdist and sdist packages and running tests on them, in a clean way. |
(To run tox, install the tox package for your distribution and run 'tox' from the toplevel git checkout.) |
Downside of tox: it explicitly ignores distribution installations of stem and ipaddress, and uses pinned pip version. So it still would be useful to know what you used for the ports test that failed, so we can get that working in a way that tests the currently install distribution libraries rather than the pinned pip ones. |
An alternate way to run tests outside of tox, btw, is something like:
But again, for that to work, the tests dir hs to be complete. Your tests failed because it was missing things. |
I am going to close this as notabug, since I believe it to be due to missing test files in the ports tree. Please let me know if you still have issues after reviewing https://github.com/mikeperry-tor/vanguards/blob/master/README_TESTS.md |
I'm still seeing this problem with version 0.2.2:
The tests are run with this command from the source directory:
What is wrong? (You said that there are "missing files in the ports tree". This is run in the source directory, ports tree doesn't have to do with this.) |
Where did your ${WRKSRC} directory come from? It looks like tests/default.conf is missing from ${WRKSRC}/tests. That file is in the git repository right here: https://github.com/mikeperry-tor/vanguards/blob/master/tests/default.conf Do you not have a complete git checkout for some reason? Did git crash or run out of disk space? |
Ok, I reproduced this by directly downloading vanguards-0.2.2.tar.gz from sdist/pip and then running the tests on that tarball. Looks like that file is not present there. Adding tests/*.conf to MANIFEST.in seems to fix this for me. Pushing a commit for that. |
Fix is in git master. Leaving this open until 0.2.3 is tagged. |
Tests work now, thanks! |
Fixed in 0.2.3 and 0.3.0 |
I'm getting these failures in the FreeBSD port:
The text was updated successfully, but these errors were encountered: