You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is likely more a question than an issue, but an issue seemed more appropriate than StackOverflow for a unit test. With current master (installed in a virtualenv with all dependencies) I get a few errors/failures, one each of which are in test_feature_availability_profiler. Specifically:
raise exceptions about the fact that the elements are not date types, instead of the expected exception.
I noticed some changes in this area in cb4c162, are the failing tests expected in master, or is it likely a platform issue?
Debugging follows, feel free to ignore
Digging in, it looks as though feature_availability_profiler wants to verify the dtype of the Series is a datetime64[ns], yet since the initial type for the only element is int, the dtype becomes an object once datetimes are mixed in, whereas if it is instantiated only with datetimes the error goes away...my quick hackery:
This is likely more a question than an issue, but an issue seemed more appropriate than StackOverflow for a unit test. With current master (installed in a virtualenv with all dependencies) I get a few errors/failures, one each of which are in
test_feature_availability_profiler
. Specifically:raise exceptions about the fact that the elements are not date types, instead of the expected exception.
I noticed some changes in this area in cb4c162, are the failing tests expected in master, or is it likely a platform issue?
Debugging follows, feel free to ignore
Digging in, it looks as though
feature_availability_profiler
wants to verify the dtype of the Series is adatetime64[ns]
, yet since the initial type for the only element isint
, the dtype becomes an object once datetimes are mixed in, whereas if it is instantiated only with datetimes the error goes away...my quick hackery:The text was updated successfully, but these errors were encountered: