-
-
Notifications
You must be signed in to change notification settings - Fork 159
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
Add Appveyor scripts #1111
Add Appveyor scripts #1111
Conversation
Current coverage is 98.84% (diff: 100%)@@ master #1111 diff @@
==========================================
Files 38 38
Lines 2830 2932 +102
Methods 0 0
Messages 0 0
Branches 0 0
==========================================
+ Hits 2796 2898 +102
Misses 34 34
Partials 0 0
|
@talumbau, Are the Travis-CI processes and the AppVeyor process going to run simultaneously? I certainly hope so because the check-in testing already takes too long. |
yes they are different services provided by different companies. They are both free for open source projects. |
@talumbau said:
I don't really care about the term of use. My question is this: when I submit a pull request are the three Travis-CI processes and the AppVeyor process(es) going to start at the same time and run in parallel? |
- handle the fact the np.dype('i4') == int (Python native int) on Windows machines. This messes up the logic in the format_print function
Github will notify both services at essentially the same time. Both services support the idea of "run these scripts on a virtual machine." Both services, therefore, need to be assigned a cloud instance for running the tests. Appveyor uses cloud machines provided by MS Azure. Travis CI uses cloud machines provided by AWS. If one service is experiencing a much heavier load than the other, they will not start at the same time, because one service will receive its virtual machine sooner than the other. There is no coordination between the services. |
The fix for #1086 via dced001 looks great, 👍 . @talumbau The provision of automated testing for Windows would also be awesome. Would it be possible, though, to use the dependencies declared in |
Yes I agree. This was mostly a copy/paste job from an existing project. I think I can do that. If it is more difficult than it seems, I'll update here and see if doing that in a follow-up PR would be ok. |
I will try to do as @zrisher suggests (create environment purely from the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we remove these lines too? Otherwise big 👍 on merging.
@rem Install optional dependencies for tests | ||
%CONDA_INSTALL% numpy=%NUMPY% pandas=%PANDAS% | ||
%CONDA_INSTALL% numba bokeh=0.12.3 toolz six mock pep8 pylint | ||
%CONDA% env update -f environment.yml | ||
|
||
%PIP_INSTALL% pytest-pep8 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@talumbau This is handled by environment.yml
:
- pip:
- pytest-pep8
So we can remove it here, correct?
|
||
%PIP_INSTALL% pytest-pep8 | ||
|
||
if %PYTHON% LSS 3.0 (%PIP_INSTALL% git+https://github.com/Blosc/castra) | ||
if %PYTHON% LSS 3.0 (%PIP_INSTALL% backports.lzma mock) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@talumbau mock
is installed via environment.yml
. Do we need backports.lzma
for Python < 3.0 on Windows? If so, should we include it in the environment file?
- remove manual install of mock - remove manual install of pytest-pep8
@zrisher I removed the additional external dependencies that you found, thanks! I think this is good to go. |
@talumbau Nice! 👍 |
No description provided.