Skip to content
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

Merged
merged 5 commits into from
Dec 29, 2016
Merged

Add Appveyor scripts #1111

merged 5 commits into from
Dec 29, 2016

Conversation

talumbau
Copy link
Member

No description provided.

@codecov-io
Copy link

codecov-io commented Dec 20, 2016

Current coverage is 98.84% (diff: 100%)

Merging #1111 into master will increase coverage by 0.04%

@@             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          

Powered by Codecov. Last update 3d24438...a95d9ed

@martinholmer
Copy link
Collaborator

@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.

@talumbau
Copy link
Member Author

yes they are different services provided by different companies. They are both free for open source projects.

@martinholmer
Copy link
Collaborator

@talumbau said:

yes they are different services provided by different companies. They are both free for open source projects.

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
@talumbau
Copy link
Member Author

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.

@talumbau
Copy link
Member Author

Resolves #1086 via dced001

@zrisher
Copy link
Contributor

zrisher commented Dec 21, 2016

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 environment.yml instead of declaring them within the build script itself, e.g. continuous_integration/setup_conda_environment.cmd:L16-26? Otherwise we're introducing for Windows the same problem you fixed for Linux in #1100.

@talumbau
Copy link
Member Author

@talumbau The provision of automated testing for Windows would also be awesome. Would it be possible, though, to use the dependencies declared in environment.yml instead of declaring them within the build script itself, e.g. continuous_integration/setup_conda_environment.cmd:L16-26? Otherwise we're introducing for Windows the same problem you fixed for Linux in #1100.

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.

@martinholmer
Copy link
Collaborator

@talumbau, When do you expect to merge pull request #1111?

@talumbau
Copy link
Member Author

I will try to do as @zrisher suggests (create environment purely from the environment.yml) some time today. If that is successful, then hopefully this can get merged today. If it's nontrivial, other's can comment if they would like to wait for the proper fix, or would rather we merge this and work on a follow-up after that.

@talumbau
Copy link
Member Author

@zrisher have a look at 649d395

I think that makes it so that on both AppVeyor and Travis CI, the config is done from environment.yml. If you are satisfied, I think we can merge.

Copy link
Contributor

@zrisher zrisher left a 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
Copy link
Contributor

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)
Copy link
Contributor

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
@talumbau
Copy link
Member Author

@zrisher I removed the additional external dependencies that you found, thanks! I think this is good to go.

@zrisher
Copy link
Contributor

zrisher commented Dec 29, 2016

@talumbau Nice! 👍

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.

4 participants