-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
CI: Failure on Appveyor Master #21102
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 strange indeed. I have a hard time thinking that change would be the cause (it was passing fine up until the last commit) but who knows. I recall there being a similar issue with the Mac builds and in the same area of testing (see #19984). I'm not sure there was ever a real resolution to that one outside of time (?) No chance we changed anything with the build environment right? I see other changes are passing... |
Yeah, it's possible this was a one-ooff (two-off?) fluke. I'm waiting to
debug further till we see additional failures.
…On Thu, May 17, 2018 at 10:13 AM, William Ayd ***@***.***> wrote:
Hmm strange indeed. I have a hard time thinking that change would be the
cause (it was passing fine up until the last commit) but who knows.
I recall there being a similar issue with the Mac builds and in the same
area of testing (see #19984
<#19984>). I'm not sure there
was ever a real resolution to that one outside of time (?)
No chance we changed anything with the build environment right? I see
other changes are passing...
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#21102 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABQHIiRaKvrANC9CKniG9sglVLGYjlRoks5tzZOLgaJpZM4UDCo2>
.
|
I did notice there's one instance in pandas/pandas/tests/io/parser/common.py Line 57 in d623ffd
|
that looks like an issue (independent of other things) |
I think I got the same problem in #21111 (Commit #ce02a40) |
https://ci.appveyor.com/project/pandas-dev/pandas/build/job/0y6fvce0al2yax06?fullLog=true#L1989
cc @WillAyd
Maybe #21066 was related? Not sure how though. Looking now.
The text was updated successfully, but these errors were encountered: