-
Notifications
You must be signed in to change notification settings - Fork 99
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
CI⚡️CD #52
base: main
Are you sure you want to change the base?
Conversation
fi | ||
|
||
# if cog.yaml changes - cog build and push. else - yolo build and push! | ||
- name: did-it-tho |
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.
did-it-tho
⭐
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.
hah the title of this step was borne out of ...debugging frustration.
but it shall stand.
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.
So happy to see this! I took the liberty of jazzing up the PR title.
I didn't review the Python code changes in depth, but the Actions workflow looks legit. 👍🏼
sudo curl -o /usr/local/bin/yolo -L "https://github.com/replicate/yolo/releases/latest/download/yolo_$(uname -s)_$(uname -m)" | ||
sudo chmod +x /usr/local/bin/yolo | ||
|
||
# yolo as hack for pushing environment variables |
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.
TIL 👀
@daanelson I'm excited to get this out in the world! What's blocking it at this point, if anything? |
a great question! two things:
|
uses: replicate/setup-cog@v1.0.3 | ||
with: | ||
token: ${{ secrets.REPLICATE_API_TOKEN }} | ||
install-cuda: false |
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.
uses: replicate/setup-cog@v1.0.3 | |
with: | |
token: ${{ secrets.REPLICATE_API_TOKEN }} | |
install-cuda: false | |
uses: replicate/setup-cog@v2 | |
with: | |
token: ${{ secrets.REPLICATE_API_TOKEN }} |
Bumped to v2 here, where CUDA drivers are not installed by default.
- name: cog-build | ||
if: steps.what-changed.outputs.cog-push == 'true' | ||
run: | | ||
cog build | ||
|
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.
- name: cog-build | |
if: steps.what-changed.outputs.cog-push == 'true' | |
run: | | |
cog build |
Can you try taking this cog build
step out entirely and letting cog push
do it implicitly? I think there is some bug in Cog right now where sometimes cog build
will fail on its own, but not if it's run as part of a push. Don't know what's that's about but I've seen it happen.
@mattt @technillogue any idea what that might be about? |
Working CI/CD + Error monitoring! Specifics:
pytest tests/test_predict.py
and you're good to go (assuming you have a machine that can run SDXL).