-
Notifications
You must be signed in to change notification settings - Fork 167
Migrate to GitHub acitions #1342
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
Migrate to GitHub acitions #1342
Conversation
@jernejfrank you can see everything in the .circleci yaml and what it references. It's similar to github workflows, but we have more flexibility on when a workflow is triggered with the github way. So shouldn't be hard to replicate. |
pyproject.toml
Outdated
| ] | ||
| dependencies = [ | ||
| "numpy", | ||
| "numpy<2", |
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 isn't good since 2.0 has been out for a while.
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.
Forgot to remove when debugging some other dependencies issues. Removed now.
| "dlt", | ||
| # furo -- install from main for now until the next release is out: | ||
| "furo @ git+https://github.com/pradyunsg/furo@main", | ||
| "furo", |
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.
+1
|
The SDK tests aren't passing because spark changed things. I think we just need to update the tests... |
@skrawcz Ah ok, then all is migrated! I thought there might be something more since the .circleci yaml doesn't mention anything about OS to test on, etc.. Also added this to the notes of the pr:
Will be fixing broken tests, but may take a while! |
1efc74e to
ffccf31
Compare
|
Right, so SDK was passing but now the CI dissapeared. Any thoughts @skrawcz? I am also thinking of limiting it to Linux (for now) since I saw that windows has some issues with package installation when using |
Can you rebase against main? (you might want to squash your commits to make that easier to do if it makes sense to squash some of them)
That's fine I think. |
Limit to linux os for now
ffccf31 to
a21f800
Compare
|
@skrawcz ok, got the tests sorted out and did a rebase. Let me know if you're happy with squash merge or need me to organize the commits :) |
.github/workflows/hamilton-main.yml
Outdated
| name: "Unit Tests" | ||
| runs-on: ${{ matrix.os }} | ||
| strategy: | ||
| fail-fast: false # will change this to true at the end, but want to see tests failing on all use cases |
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.
need to flip this?
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.
actually I think we want this to be false always.
skrawcz
left a comment
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.
Let's squash merge this into a single commit. This will make things simpler to rebase that way ; I don't think we need to keep the individual commits, right?
I usually craft a commit message, and then leave the prior squashed commits below it!
Addressing #1313 and uses uv.
I don't have access to CircleCI to see the settings there (I assume the config with jobs and worklof is only part of it, since there's no mention of OS inside), would be good to let me know if anything else needs to be configured for the github actions workflow.
Changes
How I tested this
Notes
from __future__ import annotations)Checklist