Debarshi Ray a7feb00996 test/system: Make it easier to debug why a container didn't initialize ... Currently, if a Toolbx container's entry point fails to initialize the container, there's no way to see the debug logs and error messages from the entry point: not ok 106 container: Check container starts without issues # (from function `assert_success' in file test/system/libs/bats-assert/src/assert.bash, line 114, # in test file test/system/103-container.bats, line 39) # `assert_success' failed # # -- command failed -- # status : 1 # output : # -- # Instead, from now on, they will be visible: not ok 106 container: Check container starts without issues # (from function `assert_success' in file test/system/libs/bats-assert/src/assert.bash, line 114, # in test file test/system/103-container.bats, line 39) # `assert_success' failed # # -- command failed -- # status : 1 # output (90 lines): # Failed to initialize container fedora-toolbox-38 # level=debug msg="Running as real user ID 0" # level=debug msg="Resolved absolute path to the executable as /usr/bin/toolbox" # level=debug msg="TOOLBOX_PATH is /opt/bin/toolbox" # level=debug msg="Migrating to newer Podman" # level=debug msg="Migration not needed: running inside a container" # level=debug msg="Setting up configuration" # ... # -- # https://github.com/containers/toolbox/pull/1374		2023-09-22 18:24:54 +02:00
..
system	test/system: Make it easier to debug why a container didn't initialize	2023-09-22 18:24:54 +02:00
meson.build	test/system: Test that networking works	2023-06-30 19:53:31 +02:00