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

Install with mamba, check development.txt #690

Merged
merged 1 commit into from
Feb 26, 2021
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 8 additions & 4 deletions .github/workflows/testing.yml
Original file line number Diff line number Diff line change
Expand Up @@ -18,18 +18,22 @@ jobs:
steps:
- uses: actions/checkout@v2

- name: Update dependencies if changed
- name: Reinstall dependencies if changed
run: |
cmp -s /meta.yaml localbuild/meta.yaml || (echo Dependencies differ \
cmp -s /meta.yaml localbuild/meta.yaml && cmp -s /development.txt requirements.d/development.txt || (echo Dependencies differ \
&& cat localbuild/meta.yaml \
| sed -n '/^requirements:/,/^test:/p' \
| sed -e "s/.*- //" \
| sed -e "s/menuinst.*//" \
| sed -e "s/.*://" > reqs.txt \
&& source /opt/conda/bin/activate mssenv \
Copy link
Member

Choose a reason for hiding this comment

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

I've no idea if it makes a difference to have first the env activated or the channels updated

I think that it has to be done before we install something, which in both cases is done

&& conda config --add channels conda-forge \
&& conda config --add channels defaults \
&& conda install -n mssenv --file reqs.txt --force-reinstall)

&& conda install --revision 0 \
&& conda install mamba \
&& mamba install --file reqs.txt \
&& mamba install --file requirements.d/development.txt)

- name: Run tests
timeout-minutes: 25
run: |
Expand Down