-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Contributing guideline - tests and their dependencies. #16336
Comments
Thanks @peci1 for the report. Indeed it looks like we added several tests that require specific modules without adding them to the CONTRIBUTING.mg... Linking to the travis file is a good idea indeed this way we're sure the instructions stay up to date 👍 .
Hmm that's surprising, I just tried this in a fresh container and got the full suite of tests running:
Do you see any difference with what you tried on your side ? |
|
nosetests run in Python 2.7 |
nosetests version 1.3.7 |
Unfortunately that is not enough information to help us figure out what your system setup is, can you provide the OS you are running, a pip freeze output as well as the history of commands you run before trying to run the test? |
Ubuntu 14.04.5 LTS 64bit, Python 2.7.6. Runs on Intel i7 Haswell, Dell Latitude E6450. The steps are the same as you did, just I didn't start with a fresh container, but my development machine. actionlib==1.11.9 |
Ok that's surprising. Didnt get to the point where it runs but doesnt find any test yet though. There is definitely something fishy when you have the same python packages installed from apt and from pip. I don't have much more time to look into it right now so I'd advise you to run it in a container for now or to try installing and run the python3 version of these packages to be sure to avoid weird mix-n-match of packages. Please keep us updated if you find out where the problem comes from |
A log from running nosetests in the rosdistro dir. This was achived by the following .noserc:
It seems only the test_url_validity test is picked up. |
Found the culprit! It was the pip package nose-unittest, which installs a plugin that switches the testing to unittest mode. What's weird, according to the documentation I understood that should only happen when you pass "--with-unittest", which I don't do. I also don't know how did the nose-unittest package get to my system, I don't use it directly anywhere, but maybe uninstalling it broke something. Could you please test that you can reproduce my problem by installing nose-unittest? |
Thanks @peci1 for investigating. |
So maybe it deserves a comment in the contribution guidelines? |
CONTRIBUTING.md
says:rosdistro
. That should be somehow reflected in this text excerpt. Probably linking to .travis.yml for an idea about what to install?nosetests
in the root of repo, nothing happens, no tests are executed (well, noestests tell me 1 test ran, but the runtime is ~0 sec).The text was updated successfully, but these errors were encountered: