-
Notifications
You must be signed in to change notification settings - Fork 128
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
Speed up tests on CircleCI and use pytest to run them #1804
Conversation
looking at it right now, boss 👍 |
not liking it on Jasmin: (esmvaltool) [valeriu@jasmin-sci5 esmvaltool]$ pytest
ERROR: usage: pytest [options] [file_or_dir] [file_or_dir] [...]
pytest: error: unrecognized arguments: --numprocesses
inifile: /home/users/valeriu/esmvaltool/setup.cfg
rootdir: /home/users/valeriu/esmvaltool pytest=5.4.1. Investigating now... |
OK proves out I didn't have
BTW @bouweandela you need to tell people they have to eithet pip install -e .[develop] or install whatevs the testing seesion needs before they run the tests - that's why I like python setup.py test better, dynamical installation is nice |
ah that's a |
OK it proves out you need
|
Could you try with an up to date environment, maybe just run
That's why the installation instructions come before how to run the tests (or how to use any of the other tools we recommend for developing) in the contribution guidelines.
I also liked it, but it's deprecrated pypa/setuptools#1684 |
yeah I did, I have the latest env after conda env updating and pip install -e .[develop] -ing, man. It's a number of issues that are independent of your implementation, see e.g. the |
gah, updating flake8 to 3.8.3 is still not resolving that last issue, last resort - recreating the environment from scratch. Note however that you'll need to pin |
OK good news! I recreated the env from scratch and tests run fine now, here's the difference in the envs (the older env
so I think we need to pin |
I can't reproduce CicleCI's fail at conda build stage, I ran it fine on my laptop - seems to be an issue with Julia that is creeping up only on the CI machine, weird |
what I can do is rerun the test several times over on the CI machine and I notice it dies at different stages during the R packages installation but always after 16min - is there a timeout on the CI machine for a test? |
ah! there we go https://support.circleci.com/hc/en-us/articles/360007188574-Build-has-hit-timeout-limit - and the stoopid R install output doesnt flush to stdout only at the very end |
gah! you've actually placed the condition in the config...why th is it dying then? Superconfused 😕 |
son of a gun it's the memory https://support.circleci.com/hc/en-us/articles/115014359648-Exit-code-137-Out-of-memory - any clue how to go about this? |
also @bouweandela can you pls not name the branch with the same name as a dir in ESMValTool - git was going bazooka trying to checkout |
There's a few options:
For now I went for the latter option ;-) |
You could run the conda build on your laptop if you want to check if it works |
I did and it works fine. Maybe I should stop posting comments like it's Whatsapp here 😁 BTW maybe we should start thinking about upgrading to a paid Circle account? Not off my credit card though, but surely there's a way - mooch off ISENES maybe? 😆 |
I'll plug in the Github Actions tests for ESMValTool starting tomorrow so maybe this will be tested proper and w/o $$$ there, let's see |
@bouweandela you wanna merge this? I am piggybacking on it in #1806 and will be nice to have this in |
Thanks for reviewing! |
good stuff, B-dude! 🍺 |
This pull request contains the following changes
python setup.py test
command withpytest
Tasks
yamllint
to check that your YAML files do not contain mistakesCloses #1671