-
Notifications
You must be signed in to change notification settings - Fork 295
Enable SaltBundle on SLES12-SP5 #22704
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
base: master
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change | ||||
---|---|---|---|---|---|---|
|
@@ -137,6 +137,7 @@ sub run { | |||||
reset_container_network_if_needed($engine); | ||||||
|
||||||
assert_script_run('source bci/bin/activate') if ($bci_virtualenv); | ||||||
assert_script_run('source /usr/lib/venv-salt-minion/bin/activate') if (is_sle('=12-SP5')); | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. same question as above. And please use
Suggested change
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. why ? where it is defined ? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Just don't do the parentheses because that's the common style and that is also what you used in other places in this PR There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
can you point me to the line where I haven't use them ? I don't see any There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
hard to follow this , unless it exists in written form which I can read . Another problem it should be accepted by maintainers of some certain repo . Otherwise we speaking about your personal preferences There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
According to https://progress.opensuse.org/issues/101355 apparently it's far from clear who those "maintainers" would be. But according to https://github.com/os-autoinst/os-autoinst-distri-opensuse/graphs/contributors in 24 commits you should ask dzedro ask top contributor :) There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
you said "you using" . it is not me , I never do it like that because I find this form confusing . I am fine to follow same standard when :
just pointing to one random line does not help here . I can give you contra examples in the same file There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
sorry but all this for me is just your personal view on a problem which we have . And while I respect it but I leave option for myself to have MY view on that problem There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Don't use whataboutism to push your personal preference. Be my guest to fix all non-compliant code locations in one big PR but it's not fair to expect that from a reviewer pointing out the inconsistency. I linked to a code example showing the preferred style. If you still think you want to do it differently then I will accept it for this PR but not be happy about it There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Don't use whataboutism to push your personal preference. Be my guest to fix all non-compliant code locations in one big PR but it's not fair to expect that from a reviewer pointing out the inconsistency. I linked to a code example showing the preferred style. If you still think you want to do it differently then I will accept it for this PR but not be happy about it because I prefer to use a common code style assuming that the majority of code uses the same style as proposed by me and in https://github.com/os-autoinst/os-autoinst-distri-example/blob/main/tests/boot.pm . I could be wrong and it could be that many followed a different inconsistent style over the past years. In that case we should write the new style down as the preferred style at best into static code checks and if we can't automate it then at least in https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/master/CONTRIBUTING.md |
||||||
|
||||||
record_info('Run', "Starting the tests for the following environments:\n$test_envs"); | ||||||
assert_script_run("cd /root/BCI-tests && git fetch && git reset --hard $bci_tests_branch"); | ||||||
|
@@ -158,7 +159,7 @@ sub run { | |||||
$self->run_tox_cmd($env); | ||||||
} | ||||||
|
||||||
assert_script_run('deactivate') if ($bci_virtualenv); | ||||||
assert_script_run('deactivate') if ($bci_virtualenv || is_sle('=12-SP5')); | ||||||
|
||||||
# Mark the job as failed if any of the tests failed | ||||||
die("$error_count tests failed.") if ($error_count > 0); | ||||||
|
Uh oh!
There was an error while loading. Please reload this page.