-
-
Notifications
You must be signed in to change notification settings - Fork 18.5k
TST: windows failures after #7907 (failing 27-32,26-32,26-64) #7993
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
Comments
Hmm, output looks to be parsed by dateutil, not by cython function. Will check on my windows machine later. |
ok great thanks. |
Could reproduce failure in
|
yes, make this a separate fix, hmm other tests passed? are we using same versions of datetueil/pytz? |
Hmm... looks like a If it is only the problem of display name, modifying the following condition seems to solve the case. But I'm not confident with it. Easy fix is to change the test case to use @dbew Any ideas? @jreback Regarding nanoseconds problem, is it possible that the existing cython file remains (or compile failure)? Because In Windows 7 / Python 2.7.6 / dateutil 2.2
Mac OS 10.9.4 / Python 2.7.6 / dateutil 2.2
|
@sinhrks let me make clean and see btw....do we need to update setup.py to clean that c file somehow? |
Changing How about update timestamps of |
the only issue I guess if you have an existing np_datetime.c and rebase to master, then you need to clean first, so no big deal I guess. I guess the *.pyx didn't change but the *.c did so it doesn't pick this up. no big deal, I think it will be ok. on windows, now only test_repr is failing, so that was the problem.! |
@sinhrks That looks weird. There were quite a few differences between windows and linux but the mostly came down to where Part of the difference might be that I'm not sure about modifying the line in tslib, it's a while since I looked - what did you change it to? For background, I added that to work around problems when dateutil loaded tz files from an archive but didn't put the right zone info on. Without the zone name, we can't serialize the timezone object. |
@sinhrks did we have a fix for this? |
Looked In Windows 7 / Python 2.7.6 / dateutil 2.2
Thus one possibility is to change the following line to:
But if there is any concern, leave it as |
@sinhrks Your description of the In linux, You could try it and see.. |
Thanks. I tried the above fix, and found it makes pickle/unpickle not to work properly. As this looks to be dateutil issue, let me fix the test case to avoid it. |
(ignore the pandas 0.12.0 install, this is on master, its in a separate build dir)
cc @sinhrks
related #7907
The text was updated successfully, but these errors were encountered: