-
Notifications
You must be signed in to change notification settings - Fork 5
CI: enable firefly osx #22
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
Conversation
|
This is super low stake (we do run the tests with the linux VM), so I'll just wait for the new release before merging this. |
|
Yeah, I'm about to create a PR to improve package infrastructure a bit and then I'll cut a release probably sometime next week. On a related thought, can you trigger your pipeline once I have that upcoming PR merged for a final test? |
Sure, and I'm also happy to trigger it on your PR before merging it. |
ae679c2 to
00a0d47
Compare
|
Ahh, this smoked out a bug in the new CI system :) |
tutorials/requirements.txt
Outdated
| ray | ||
| s3fs | ||
| firefly-client | ||
| git+https://github.com/Caltech-IPAC/firefly_client@FIREFLY-1527-update-package-config#egg=firefly_client |
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.
This can now safely go back to firefly-client. Thanks for all the testing!
1154f3a to
3951399
Compare
|
Great! all checks passed |
CI: enable firefly osx ff38f99
This is to test the fix from Caltech-IPAC/firefly_client#61
More context: #10 (comment) and below
cc @jaladh-singhal