Skip to content

failing microsecond formatter test #4179

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

Closed
cpcloud opened this issue Jul 9, 2013 · 1 comment
Closed

failing microsecond formatter test #4179

cpcloud opened this issue Jul 9, 2013 · 1 comment
Labels
Datetime Datetime data dtype Dtype Conversions Unexpected or buggy dtype conversions Output-Formatting __repr__ of pandas objects, to_string

Comments

@cpcloud
Copy link
Member

cpcloud commented Jul 9, 2013

FAIL: pandas.tseries.tests.test_timeseries:TestTimeSeries.test_to_datetime_format_microsecond
  gvim -f +836 pandas/tseries/tests/test_timeseries.py  # test_to_datetime_format_microsecond
    self.assertEqual(result, exp)
AssertionError: Timestamp('2011-03-31 23:24:13.516352', tz=None) != datetime.datetime(2011, 4, 1, 0, 0, 1, 978000)

1 test, 1 failure, 0 errors in 0.0s

(i changed to assertEqual)

@jorisvandenbossche
Copy link
Member

@cpcloud Strange, it is exactly the test that I introduced in PR #4166 and which should be fixed by that PR that is failing. Did you rebuild the cython files?

Because the Timestamp in the Error message is exactly the Timestamp you get before my fix, so it seems the fix was not applied on your system.

@cpcloud cpcloud closed this as completed Jul 9, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Datetime Datetime data dtype Dtype Conversions Unexpected or buggy dtype conversions Output-Formatting __repr__ of pandas objects, to_string
Projects
None yet
Development

No branches or pull requests

2 participants