-
-
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
tmpdir name clashes with parametrization #2447
Comments
This should be fixed with the release of |
Sorry for the delay, but this is still happening with
I used the reproduction I posted earlier as |
That's strange, I can reproduce it with |
I get a huge stack trace with pytest 3.1.2, py 1.4.34 using MacOS 10.12.5 using Darius's code. |
Thanks @Dude-x. That's unfortunate, I can't reproduce it on Windows using |
@nicoddemus afair osx does unicode normalization for path names - which is even worse than just case normalization and could be the source of the issue |
Sorry, what do you mean by that? |
HFS+ stores filenames in decomposed form, so an umlaut for example will be turned from a single codepoint to 2 |
I see, thanks. I wonder if that's the problem though, the example posted by @DariusL only uses ASCII. Also doesn't the form how the filenames are stored abstract away when obtaining the file names ( |
true, as of now i can only guess as well |
This should be fixed after |
Seems to pass correctly with
which I get with
Looks like a fix to me. |
Sweeeeeeeeet |
It seems that tmpdir numbering fails when fixtures have similar start names.
Reproduction:
Result:
The error is the similar for all:
Basically,
test_asdasds[emulator-5554-JasminTest]
,test_asdasds[emulator-5554-JAssert]
andtest_asdasds[emulator-5554-JAssert2]
tried to use the same temporary directorytest_asdasdsa_emulator_5554_JA0
, the last two failing.Seems to be directly related to full test name length - if I shorten the test name, I only get two errors, where the names have a longer match:
Running pytest 3.1.0, MacOS 10.12.6 beta.
Fresh virtualenv,
The text was updated successfully, but these errors were encountered: