osmith has uploaded this change for review.

View Change

testenv: use proper envtype for --shell

When using --podman --shell to run an interactive shell after the
testsuite is done (for debugging), use the proper envtype depending on
--binary-repo being used or not, instead of always assuming the
binary-repo envtype.

Fixes: b728a7fb ("testenv: cmd: init_env: split up by envtype")
Change-Id: I7ef93c452a0696a18e0875e40465ef5c985f6e86
---
M _testenv/testenv/podman.py
1 file changed, 8 insertions(+), 1 deletion(-)

git pull ssh://gerrit.osmocom.org:29418/osmo-ttcn3-hacks refs/changes/48/43848/1

diff --git a/_testenv/testenv/podman.py b/_testenv/testenv/podman.py
index 7b5e734..f6264d5 100644
--- a/_testenv/testenv/podman.py
+++ b/_testenv/testenv/podman.py
@@ -367,7 +367,14 @@
         logging.info("Running interactive shell before stopping container (--shell)")
 
         # stdin=None: override stdin=/dev/null, so we can type into the shell
-        exec_cmd(["bash"], ["-i"], cwd=testenv.testdir.testdir, stdin=None, check=False)
+        exec_cmd(
+            ["bash"],
+            ["-i"],
+            cwd=testenv.testdir.testdir,
+            stdin=None,
+            check=False,
+            envtype="binary_repo" if testenv.args.binary_repo else "osmo_dev",
+        )
 
         run_shell_on_stop = False
 

To view, visit change 43848. To unsubscribe, or for help writing mail filters, visit settings.