- Detect VS devcmd error (missing VS)
- Detect missing python install
- Show commands executed
- Removed pause (blocking CI usage)
Details
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
lgtm
llvm/utils/release/build_llvm_release.bat | ||
---|---|---|
69 | I liked this, but I can see how it doesn't make sense for everyone. |
llvm/utils/release/build_llvm_release.bat | ||
---|---|---|
128 | Why this added @echo on here? Does call "%vsdevcmd%" affect the echo mode of this surrounding script? |
llvm/utils/release/build_llvm_release.bat | ||
---|---|---|
69 | I'm open to discuss this. | |
128 | Alas yes. Any script called with call "pollutes" current environment, including for echoing commands. |
llvm/utils/release/build_llvm_release.bat | ||
---|---|---|
69 | I think dropping it is fine. |
llvm/utils/release/build_llvm_release.bat | ||
---|---|---|
69 | FWIW, if there's an easy way to check if the current terminal is interactive or not (it's fairly easy to do this for unix shell scripts at least), it could be kept conditionally for such cases I think. | |
128 | Ah, right - it's been a couple decades since I spent more time thinking about the intricacies of bat scripts... Then this sounds reasonable to me. |
llvm/utils/release/build_llvm_release.bat | ||
---|---|---|
69 | It probably exists for batch indeed. But when used really interactively (like use case I was talking about), the fact it stops is not handy. |
@hans It seems build failed because of a sporadic issues (not related to this patch).
How are we suppose to deal with this? Do you have rights to trigger it again?
Once built, is it automatically rebase/merged on trunk, or do you do trigger this by clicking somewhere?
That's my first submission using phabricator, so sorry if the question is naive (didn't find answer in llvm documentation).
Sadly it often fails for unrelated reasons. Ignoring it is fine, especially since it doesn't run this script at all.
Once built, is it automatically rebase/merged on trunk, or do you do trigger this by clicking somewhere?
There is no automatic way to commit/push. Since it's your first patch I assume you don't have commit access, so I will commit it on your behalf (see https://llvm.org/docs/DeveloperPolicy.html#obtaining-commit-access).
@hans
Thanks, I thought is was "blocking", like some other review systems.
For commit access, I'll probably request it somewhere in the future (beyond work on this script).
Thanks for submitting it for me.
I liked this, but I can see how it doesn't make sense for everyone.