-
Notifications
You must be signed in to change notification settings - Fork 55
Build swift-inspect in the toolchain workflow. #557
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
The standalone workflow has been tested https://github.com/hjyamauchi/swift-build/actions/runs/5149995509 |
86729cc
to
708ad67
Compare
The workflow worked (except that the release step failed due to the release tag conflict with the previous run, which I think is expected) at https://github.com/thebrowsercompany/swift-build/actions/runs/5159007140 |
708ad67
to
651188a
Compare
a0abdad
to
1b2aedf
Compare
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
0b97399
to
5d1b38d
Compare
OK, done. |
Why does |
Not obvious to me why. They don't look depending on each other. Also it's odd that they are failing because of the .exe file not being found. I think the upload-artfact doesn't work with symlinks but it worked for swift-format in the previous runs? |
5d1b38d
to
29a8f44
Compare
Updated to fix the .exe path. |
f65c233
to
ed97da5
Compare
@hjyamauchi - mind rebasing the change? |
ed97da5
to
deb909e
Compare
Rebased. Testing at https://github.com/thebrowsercompany/swift-build/actions/runs/5173064838 |
Build swift-inspect under the installer setup at the end like swift-format.