Project

General

Profile

Actions

Bug #21990

open

Log files arv-mount.txt, crunchstat.txt, and hoststat.txt no longer show timestamps

Added by Zoë Ma 12 days ago. Updated 12 days ago.

Status:
New
Priority:
Normal
Assigned To:
-
Category:
Crunch
Target version:
-
Story points:
-

Description

Symptom -- apparently related to issue #21834 - the process log files arv-mount.txt, crunchstat.txt, and hoststat.txt `are not showing the timestamps as they used to do in v2.7.3. This has cascading effect of making crunchstat_summary unable to parse the output, see source:tools/crunchstat-summary/crunchstat_summary/summarizer.py@7f01a21e3f250027510d16c32acd0c62173f1fec#L109 (I think at the end of the run the arv-mount.txt and crunchstat.txt files are used to generate the report). With the timestamp missing, the regular expression in L86 may match log lines by accident, but without capturing valid values for the groups, so we will hit that raise in the highlighted line. This will also be visible in WB2 as a warning message about failing to generate usage report.

The expected behavior (based on my understanding) is to consistently prefix each line in all of the applicable output logs with the timestamp, and the usage report can be created from them.

I've attached two output log collections, one with what I think is the "correct" behavior (from a run on v.2.7.3) and the other with missing timestamps (generated by the dev version).


Files

00incorrect log for container xlbrs-dz642-0v7mqrlf2tuajyo.tar.gz (9.95 KB) 00incorrect log for container xlbrs-dz642-0v7mqrlf2tuajyo.tar.gz log collection with timestamps missing in 3 files Zoë Ma, 07/09/2024 10:14 AM
01correct log for container xlbrs-dz642-t0s46rogec7zzy2.tar.gz (19.3 KB) 01correct log for container xlbrs-dz642-t0s46rogec7zzy2.tar.gz log collection from v2.7.3 showing timestamps in all relevant files Zoë Ma, 07/09/2024 10:15 AM
Actions #1

Updated by Peter Amstutz 12 days ago

You are using development packages, correct? Have you updated them recently? Because this sounds exactly like #21833 and #21834 which are fixed in main.

You need to update crunch-run.

Actions #2

Updated by Zoë Ma 12 days ago

Peter Amstutz wrote in #note-1:

You are using development packages, correct? Have you updated them recently? Because this sounds exactly like #21833 and #21834 which are fixed in main.

You need to update crunch-run.

I was using crunch-run 2.8.0~dev20240703133808 (go1.21.10), from the jammy-dev repo.

Actions

Also available in: Atom PDF