-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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] Fix mac release and integrate windows release into github #2641
Conversation
/format |
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.
LGTM!
Co-authored-by: Ye Kuang <[email protected]>
@@ -5,8 +5,8 @@ on: | |||
types: [published] |
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.
I hope we can trigger the nightly path for each merge-to-master
event, and the official build path for a release. Is it possible to achieve that?
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.
Yes, I'm working on this. Seems that time-based nightly release and merge-based nightly release can both work.
export PATH=$TAICHI_REPO_DIR/taichi-llvm/bin/:$PATH | ||
NUM_WHL=`ls dist/*.whl | wc -l` | ||
if [ $NUM_WHL -ne 1 ]; then echo 'ERROR: created more than 1 whl.' && exit 1 ; fi | ||
pip install dist/*.whl |
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.
Oh sorry for the late review, we actually want to preserve this logic :P Since we want to test a taichi installed from our built wheel (python setup.py develop is local dev mode which might slightly differ from the content inside the wheel). So we need another PR to bring this logic back.
In fact it's indeed better to unify all the CI to first build the wheel and test from there. (compared to testing in dev mode).
Related issue = #2634