Closed mr-cal closed 1 year ago
Hello,
Do you talk about this PR:https://github.com/snapcore/snapcraft/pull/3891 ?
@mr-cal I managed to display only the outer instance's log when Rockcraft fails.
I think it's normal for the other one since we use the verbose mode. WDYT
Do you talk about this PR:https://github.com/snapcore/snapcraft/pull/3891 ?
Yep, that looks like the right PR!
I think it's normal for the other one since we use the verbose mode. WDYT
I'm interpreting this as "the outer log location is always logged when running rockcraft
, since the default verbosity is verbose". If that's what you mean, then I agree that it is the correct behavior.
This issue needs to be closed, no?
True, thanks! closed by #170
When rockcraft starts, the location of the log file is shown twice, from the the outer rockcraft and managed rockcraft processes:
Logging execution to '/home/developer/.cache/rockcraft/log/rockcraft-20221103-105727.504666.log'
Logging execution to '/tmp/rockcraft.log'
This also occurs when rockcraft fails, the location of the two log files appear:
Full execution log: '/tmp/rockcraft.log'
from inside the instanceFull execution log: '/home/developer/.cache/rockcraft/log/rockcraft-20221103-105727.504666.log'
from outside the instanceOnly the outer instance's log location should be displayed.
The collection of log files from the managed rockcraft instance is recent feature (I added it here and here).
I recall that snapcraft or charmcraft had a similar issue recently (I haven't searched for the bug or PR), so the solution from one of those projects can be leveraged.