fix ci tracing tests silently failing

Signed-off-by: Doru Blânzeanu <[email protected]>

Author: dblnz

Justfile

@@ -204,10 +204,14 @@ test-rust-tracing target=default-target features="":
     just build-rust-guests {{ target }} trace_guest
     just move-rust-guests {{ target }}
     # Run hello-world example with tracing enabled to get the trace output
-    # Capture the trace file path and print use it afterwards to run cargo run -p trace_dump
-    cargo run --profile={{ if target == "debug" { "dev" } else { target } }} --example hello-world --features {{ if features =="" {'trace_guest'} else { "trace_guest," + features } }} \
-        | sed -n 's/.*Creating trace file at: \(.*\)/\1/p' \
-        | xargs -I {} cargo run -p trace_dump ./{{ simpleguest_source }}/{{ target }}/simpleguest {} list_frames
+    TRACE_OUTPUT="$(cargo run --profile={{ if target == "debug" { "dev" } else { target } }} --example hello-world --features {{ if features =="" {"trace_guest"} else { "trace_guest," + features } }})" && \
+        TRACE_FILE="$(echo "$TRACE_OUTPUT" | grep -oE 'Creating trace file at: [^ ]+' | awk -F': ' '{print $2}')" && \
+        echo "$TRACE_OUTPUT" && \
+        if [ -z "$TRACE_FILE" ]; then \
+            echo "Error: Could not extract trace file path from output." >&2 ; \
+            exit 1 ; \
+        fi && \
+        cargo run -p trace_dump ./{{ simpleguest_source }}/{{ target }}/simpleguest "$TRACE_FILE" list_frames
 
     # Rebuild the tracing guests without the tracing feature
     # This is to ensure that the tracing feature does not affect the other tests