From f424b29464a5e4cd4333150826fa3c67c101d8f6 Mon Sep 17 00:00:00 2001 From: Vanja Pejovic Date: Wed, 5 Feb 2025 17:13:16 -0500 Subject: [PATCH] Update debug logging flags in firecracker/README (#8318) The old flag doesn't exist any more, and these are useful for understanding what broke in a failing test. --- .../remote_execution/containers/firecracker/README.md | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/enterprise/server/remote_execution/containers/firecracker/README.md b/enterprise/server/remote_execution/containers/firecracker/README.md index f3ca9110785..4e6c86b8c13 100644 --- a/enterprise/server/remote_execution/containers/firecracker/README.md +++ b/enterprise/server/remote_execution/containers/firecracker/README.md @@ -40,13 +40,16 @@ If you want to test workflows locally with firecracker, make sure to set You can run Firecracker in debug mode to see more detailed VM logs, including logs from the init binary and vmexec server. -To run in debug mode, set `--executor.firecracker_debug_mode=true` -on the executor, or pass `--test_arg=--executor.firecracker_debug_mode=true` +To run in debug mode, set `--executor.firecracker_debug_stream_vm_logs=true` +on the executor, or pass `--test_arg=--executor.firecracker_debug_stream_vm_logs=true` to `bazel test`. It's useful to use debug mode whenever the executor can't connect to the VM (indicating the VM might have crashed). +You can also stream test outputs to stdout with `--debug_stream_command_outputs` +passed either to the executor or as part of `--test_arg=...`. + ### SSH into a VM You can run arbitrary commands inside a VM either by running a custom