Commit 2a19d45
committed
run.py: stop hiding sandbox and recommend --debug on sandbox failure
As discussed in systemd#3948 and systemd#3992, logging commands failing in a sandbox
without ever mentioning that a sandbox was in use is misleading and very
time-consuming; notably because paths look real but they are not.
To remove this confusion and cost, simply add one short line mentioning
that a sandbox was involved when the failure happened + recommend to
re-run with --debug to display bind mounts and other important
information.
Also separate the command and error message on different lines for
better readability and re-usability.
Just for the record: before commit 7e7a3c7 ("Don't log sandbox for
every command"), `run.py` was logging sandbox commands every time which
was too verbose and unreadable. That commit said "... but still log the
full sandbox if a command fails" and it did that do in `__init__.py` -
but not always in `run.py`. After that commit, the sandbox was logged by
`run.py` only in --debug mode and became completely invisible otherwise.
Signed-off-by: Marc Herbert <marc.herbert@intel.com>1 parent d44aae1 commit 2a19d45
1 file changed
+13
-8
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
106 | 106 | | |
107 | 107 | | |
108 | 108 | | |
| 109 | + | |
| 110 | + | |
| 111 | + | |
| 112 | + | |
| 113 | + | |
| 114 | + | |
| 115 | + | |
| 116 | + | |
| 117 | + | |
| 118 | + | |
| 119 | + | |
109 | 120 | | |
110 | 121 | | |
111 | 122 | | |
112 | 123 | | |
113 | | - | |
114 | | - | |
115 | | - | |
116 | | - | |
| 124 | + | |
117 | 125 | | |
118 | 126 | | |
119 | 127 | | |
| |||
126 | 134 | | |
127 | 135 | | |
128 | 136 | | |
129 | | - | |
130 | | - | |
131 | | - | |
132 | | - | |
| 137 | + | |
133 | 138 | | |
134 | 139 | | |
135 | 140 | | |
| |||
0 commit comments