Hello Rebecca, >Running just the affected test files (in installed -6) produced no >failures in ~350 attempts. The build of -7 succeeded on amd64; it >failed on ppc64, but as the log isn't available yet, I don't know if >it's this bug.
I don't think so, when log is not available it might mean a powercycle of the builder, or something else (e.g. space issue).It has been probably automatically retried and now it passed >While both tests involve time-related dtypes, the test data is a fixed >set not the current time, so the time of build probably isn't what >decides which runs fail. > >Does anyone have a reproducible way to trigger this error? nope, and looks like they are all good now :) close this bug and keep an eye for the future might be the bet thing to do I would say...thanks for the effort and for unbreaking the pandas loop! G.
