fix: handle v3004+ which can be installed to any location on Windows#340
fix: handle v3004+ which can be installed to any location on Windows#340krionbsd merged 6 commits intosaltstack:masterfrom
Conversation
v3004 successful test run-----> Starting Test Kitchen (v3.2.2) -----> Cleaning up any prior instances of -----> Destroying ... Finished destroying (0m0.00s). -----> Testing -----> Creating ... Bringing machine 'default' up with 'virtualbox' provider... ==> default: Cloning VM...�[K==> default: Matching MAC address for NAT networking... -----> Converging ... -----> Setting up ... tests/integration/test_git.py::test_pkg[git] SKIPPED (Skip on freebs...) [ 7%] =============================== warnings summary =============================== -- Docs: https://docs.pytest.org/en/stable/warnings.html |
v3003.3 successful test run-----> Starting Test Kitchen (v3.2.2) -----> Cleaning up any prior instances of -----> Destroying ... Finished destroying (0m0.00s). -----> Testing -----> Creating ... Bringing machine 'default' up with 'virtualbox' provider... ==> default: Cloning VM...�[K==> default: Matching MAC address for NAT networking... -----> Converging ... -----> Setting up ... tests/integration/test_git.py::test_pkg[git] SKIPPED (Skip on freebs...) [ 7%] =============================== warnings summary =============================== -- Docs: https://docs.pytest.org/en/stable/warnings.html |
|
The Debian |
f41c495 to
a157be9
Compare
…lt`) This reverts commit 17762bc. Fixed in `kitchen-salt`: * saltstack/kitchen-salt#340
This reverts commit 17762bc. Fixed in `kitchen-salt`: * saltstack/kitchen-salt#340
The Windows
salt-call.batexecutable was hardcoded toC:\saltbut this is no longer appropriate sincev3004allows to install Salt executables to any location. Answer is to rely on findingsalt-call.batin the system PATH environment variable.