-
Notifications
You must be signed in to change notification settings - Fork 422
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
[testing-on-gke part 6.7] Improvements in run script #2498
base: master
Are you sure you want to change the base?
[testing-on-gke part 6.7] Improvements in run script #2498
Conversation
69dd733
to
06df415
Compare
b77d5ef
to
bf0661a
Compare
06df415
to
fb05a44
Compare
c49f080
to
ac9c164
Compare
fb05a44
to
2d72ed3
Compare
ac9c164
to
4d3d3fb
Compare
2d72ed3
to
b94e91f
Compare
4d3d3fb
to
d77db67
Compare
b94e91f
to
58948ee
Compare
d77db67
to
5825918
Compare
b92fa47
to
0364b7c
Compare
5825918
to
ee6d69c
Compare
0364b7c
to
9613a45
Compare
ee6d69c
to
c93fde8
Compare
9613a45
to
302395c
Compare
c93fde8
to
39ece93
Compare
302395c
to
5cad921
Compare
39ece93
to
5d75bca
Compare
d4a44f3
to
db1581a
Compare
9329aae
to
b4db597
Compare
Option: force_update_gcsfuse_code Default: false This applies when $gcsfuse_src_dir has been passed, or when $src_dir/gcsfuse already exists.
Adds logs for missing sudoless-docker, helpful instruction to install it, and then to re-run the script.
b4db597
to
d141ea7
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #2498 +/- ##
==========================================
- Coverage 78.32% 78.28% -0.05%
==========================================
Files 107 107
Lines 11770 11770
==========================================
- Hits 9219 9214 -5
- Misses 2068 2071 +3
- Partials 483 485 +2
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
This reverts commit 6fa2ad2. Reverting this because the above commit exposed PII in form of the gcsfuse-internal project IDs and numbers.
The run-gke-tests script should fail if exactly one out of project_id and project_number has been set. It will error out in such as a case.
Add 'Error: ' prefix in all the error logs for easy spotting in log files.
test -n "${project_number}" || export project_number=${DEFAULT_PROJECT_NUMBER} | ||
if test -n "${project_id}"; then | ||
if test -z "${project_number}"; then | ||
echo "Error: project_id was set, but not project_number. Either both should be specified, or neither." |
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.
Should we output these errors to stderr?
@@ -285,19 +343,19 @@ function validateMachineConfig() { | |||
case "${machine_type}" in | |||
"n2-standard-96") | |||
if [ ${num_ssd} -ne 0 -a ${num_ssd} -ne 16 -a ${num_ssd} -ne 24 ]; then | |||
echo "Unsupported num-ssd "${num_ssd}" with given machine-type "${machine_type}". It should be 0, 16 or 24" | |||
echo "Error: Unsupported num-ssd "${num_ssd}" with given machine-type "${machine_type}". It should be 0, 16 or 24" |
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.
Same as before - Should we output these errors to stderr?
Description
Improvements in run-script:
Error:
as prefix.This is on top of #2497 and is followed up in #2499, #2322, and #2528 .
Link to the issue in case of a bug fix.
NA
Testing details