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

PGSU not available for conda #3900

Closed
csadorf opened this issue Apr 7, 2020 · 7 comments
Closed

PGSU not available for conda #3900

csadorf opened this issue Apr 7, 2020 · 7 comments
Assignees
Labels
priority/critical-blocking must be resolved before next release topic/dependencies

Comments

@csadorf
Copy link
Contributor

csadorf commented Apr 7, 2020

The pgsu dependency cannot be installed with conda: https://github.com/aiidateam/aiida-core/runs/566297364?check_suite_focus=true !

@ltalirz Can you create a conda-forge package, please?
@sphuber Can you make sure to add me as a reviewer when dependencies are changed? I'm not sure why the codeowner file did not trigger my review.

@csadorf csadorf added priority/critical-blocking must be resolved before next release topic/dependencies labels Apr 7, 2020
@csadorf csadorf self-assigned this Apr 7, 2020
@chrisjsewell
Copy link
Member

This is what I mentioned in #3613 (comment). I still feel you shouldn't be "allowed" to merge to develop until .github/workflows/test-install.yml passes, rather than these tests only being triggered after the merge?

@csadorf
Copy link
Contributor Author

csadorf commented Apr 7, 2020

@chrisjsewell It actually should have been triggered:

push:
paths:
- 'setup.*'
- 'environment.yml'
- '**/requirements*.txt'
- 'pyproject.toml'
- 'util/dependency_management.py'
- '.github/workflows/test-install.yml'

I assume it didn't because it was a pull request? I'm still a bit confused about the github actions push trigger.

@chrisjsewell
Copy link
Member

chrisjsewell commented Apr 7, 2020

I assume it didn't because it was a pull request?

Yep exactly (as I understand it) push only trigger when a commit is made to a branch of aiidateam/aiida-core (not forks), rather than pull-request trigger when commits are made to any forks/branches associated with open PRs.

@ltalirz
Copy link
Member

ltalirz commented Apr 7, 2020

the PR is open since 2 days ago conda-forge/staged-recipes#11226
waiting for it to be merged

@csadorf
Copy link
Contributor Author

csadorf commented Apr 7, 2020

I assume it didn't because it was a pull request?

Yep exactly (as I understand it) push only trigger when a commit is made to a branch of aiidateam/aiida-core (not forks), rather than pull-request trigger when commits are made to any forks/branches associated with open PRs.

@chrisjsewell So no other way than to just duplicate everything? Or should we just replace push with pull_request considering the use case here?

@chrisjsewell
Copy link
Member

@chrisjsewell So no other way than to just duplicate everything? Or should we just replace push with pull_request considering the use case here?

Given that its also be run as a cron job anyway, I'd just replace with pull_request.

FYI here's a related GitHub Forum Post, that I've looked at before in relation to other projects. Its annoying that if you make a PR from a branch (not fork), you end up with duplicates of all the tests, but it looks like there is no good solution for that.

@ltalirz
Copy link
Member

ltalirz commented Apr 15, 2020

@ltalirz ltalirz closed this as completed Apr 15, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority/critical-blocking must be resolved before next release topic/dependencies
Projects
None yet
Development

No branches or pull requests

3 participants