Skip to content

MAINT Configure Windows CI using AppVeyor #260

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
wants to merge 20 commits into from
Closed

MAINT Configure Windows CI using AppVeyor #260

wants to merge 20 commits into from

Conversation

jacksonllee
Copy link
Contributor

IT support has turned on AppVeyor for CI in Windows. This PR configures that, based on what we already have for Circle CI.

Resolves #10.

jacksonlee-civis and others added 20 commits May 29, 2018 11:51
by checking just whether or not poller is called.
Asserting a specific call count for a given sleep time
is not practical, because of different execution/testing environments
(Circle CI versus AppVeyor, for example).
Because polling_interval is 0.01, setting sleep time of 0.02s
should (hopefully) be long enough to register at least 1
poller call.
feather-format depends on pyarrow, which does not have
Windows packages for python version < 3.5.
See https://arrow.apache.org/docs/python/install.html
The archive name is a member file inside a zip file.
It'd seem more reasonable to have it different than
the zip file name.
@jacksonllee
Copy link
Contributor Author

This is the same as #258. Creating this PR just to see if AppVeyor builds are triggered (which apparently are not...)

@jacksonllee jacksonllee deleted the set-up-windows-continuous-integration-2 branch June 13, 2018 20:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants