ci: add 'NO_INSTALL' flag to ci/rust-version.sh#6663
Conversation
6afb1f0 to
a795385
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #6663 +/- ##
=======================================
Coverage 83.3% 83.3%
=======================================
Files 849 849
Lines 379469 379469
=======================================
+ Hits 316234 316266 +32
+ Misses 63235 63203 -32 🚀 New features to boost your workflow:
|
| return | ||
| fi | ||
|
|
||
| [[ -z $1 ]] || ( |
There was a problem hiding this comment.
Why does this code block even run, since ci/docker/env.sh sources this script with no args?
There was a problem hiding this comment.
yeah… maybe I should extract the env from the actual logic 🤔. actually, I’m in a bit of a dilemma. we’ve already advertised using ci/rust-version.sh to install https://github.com/anza-xyz/agave/blob/master/README.md?plain=1#L28. also, I think we’ve gotten used to updating the rust stable/nightly version in this file. splitting it might open a long thread 🙈 so I decide to just introduce a no harm env to control the flow
There was a problem hiding this comment.
Yeah I'm fine with merging this as a workaround.
But I really don't see how this it's printing the ignoring unknown argument warning in this case, since that whole code block should be skipped if -z $1. Do you understand what's happening to make it print the warning?
There was a problem hiding this comment.
afaik, when we source a file, it shares the same context. if we don’t reset the args, they will be inherited by the script.
There was a problem hiding this comment.
Ah yeah I just reproduced this locally... I didn't know sourced scripts picked up the args from the parent.
Problem
there is a confusing message in our build:

the message comes from
agave/ci/rust-version.sh
Line 65 in 557bfcb
Summary of Changes
add an option, NO_INSTALL, in the script