-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
py.test 2.1.0 causes new errors #60
Comments
Original comment by Brian O'Neill (BitBucket: sfbrian, GitHub: sfbrian): Here is another example. Basically i'm trying to collect my smoke tests and run them. It doesn't seem to be agreeing with my imports? {{{ [boneill@boneills-MacBook-Pro apitest (dev)]$ py.test -k smoke
}}} I could try writing a standalone test that might cause this, but I think it's the import at the top that is causing issues. |
Original comment by Brian O'Neill (BitBucket: sfbrian, GitHub: sfbrian): Here is another example where it is running on a remote machine that doesn't have as much write access: {{{
}}} |
Original comment by Brian O'Neill (BitBucket: sfbrian, GitHub: sfbrian): Still getting the same "file exists" errors {{{ Why is pytest trying to create directories? |
Original comment by Benjamin Peterson (BitBucket: gutworth, GitHub: gutworth): I'm unable to reproduce this on Linux mostly because I'm not exactly sure what you're running. This, for example, works for me: {{{ def test_x(): pass |
Original comment by Brian O'Neill (BitBucket: sfbrian, GitHub: sfbrian): I don't think we are using python_files. Some of our tests manipulate a file here or there. I definitely know that our tests aren't in zip or eggs. It looks like pytest is trying to create a directory (and overwrite it) for my imports and not just the test files. |
Original comment by holger krekel (BitBucket: hpk42, GitHub: hpk42): can you retry with mercurial head or "pip install -i http://pypi.testrun.org -U pytest" and send a "pytestdebug.log" that you can create with a "py.test --debug ..." invocation? from the trace we hopefully understand better what's going on - have added some more info there. |
Original comment by Brian O'Neill (BitBucket: sfbrian, GitHub: sfbrian): Attached the log. I took a brief look and this around here looks to be the problem: {{{ }}} |
Encode strings to handle unicode
Originally reported by: Brian O'Neill (BitBucket: sfbrian, GitHub: sfbrian)
After upgrading to 2.1.0, when running the same tests I normal run I get a bunch of new errors:
I'm not sure what is causing these new errors.
The text was updated successfully, but these errors were encountered: