Skip to content

Windows CI #23182

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

Merged
merged 15 commits into from
Oct 18, 2018
4 changes: 1 addition & 3 deletions ci/azure-windows-36.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -6,18 +6,16 @@ dependencies:
- blosc
- bottleneck
- fastparquet
- feather-format
- matplotlib
- numexpr
- numpy=1.14*
- openpyxl=2.5.5
- pyarrow
- pyarrow=0.9.0
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I could reproduce #23180 and the first fix I tried (boost-cpp<1.67) worked. Pinning pyarrow is probably not gonna change things, because the offending error happens with 0.9.0 anyway.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

https://repo.continuum.io/pkgs/main/win-64/ has a package for pyarrow 0.9.0. I'm hoping that removing feather-format will keep us in main, not not conda-forge for these packages.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

But, if this fails I'll try pinning to boost-cpp<1.67

Copy link
Contributor Author

@TomAugspurger TomAugspurger Oct 16, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It failed. Trying a boost-cpp pin now.

- pytables
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you try vc=14.0 (without the pragma stuff)? the last working build had that, while the newer ones have 14.1. Plus, the notna definition still didn't fix the errors in the WinPy36 build.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the notna definition still didn't fix the errors in the WinPy36 build.

29f392c had a bug (not isn't valid C++).

I think this turned up a real bug that's hitting users / will hit users, depending on how things are compiled. Probably best to fix it.

- python-dateutil
- python=3.6.*
- pytz
- scipy
- thrift=0.10*
- xlrd
- xlsxwriter
- xlwt
Expand Down