From: Daniel Kral <d.kral@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH ha-manager 0/7] some test logging output improvements
Date: Fri, 17 Apr 2026 14:27:15 +0200 [thread overview]
Message-ID: <20260417122728.330123-1-d.kral@proxmox.com> (raw)
This patch series makes some improvements on how tests output their
logs, especially to make any unexpected warnings fail the test cases.
This catches the typical 'uninitialized variable used' and other Perl
warnings, which would have gone unnoticed beforehand as there's much
more output on STDOUT than STDERR.
This is a small QoL improvement when working on the HA stack because it
catches newly introduced perl warnings early and a
git rebase master --exec 'make clean && make deb'
with enough test branch coverage should give at least some confidence
that the individual patches are ordered correctly and do not introduce
Perl warnings.
Also a small patch at the end I've used locally for some time to better
highlight the diff output for failed test cases.
Daniel Kral (7):
sim: always limit the priority level to 4 characters
consistently use correct priority levels for log calls
sim: hardware: factor common service lock hash access in
unlock_service
use log with warning priority instead of warn where possible
pve-ha-tester: capture and fail for unexpected perl warnings
test: ha-tester: use consistent word casing for failed test messages
test: ha-tester: use colorized diff for unexpected test log outputs
src/PVE/HA/Env.pm | 2 ++
src/PVE/HA/Env/PVE2.pm | 4 ++--
src/PVE/HA/Fence.pm | 2 +-
src/PVE/HA/Manager.pm | 6 +++---
src/PVE/HA/Resources/PVEVM.pm | 2 +-
src/PVE/HA/Sim/Env.pm | 2 ++
src/PVE/HA/Sim/Hardware.pm | 17 ++++++++++-------
src/PVE/HA/Sim/RTEnv.pm | 1 +
src/PVE/HA/Sim/RTHardware.pm | 1 +
src/PVE/HA/Sim/Resources/VirtCT.pm | 2 +-
src/PVE/HA/Sim/TestHardware.pm | 1 +
src/pve-ha-tester | 8 ++++++++
src/test/ha-tester.pl | 6 +++---
src/test/test-locked-service2/log.expect | 9 +++++++++
14 files changed, 45 insertions(+), 18 deletions(-)
--
2.47.3
next reply other threads:[~2026-04-17 12:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-17 12:27 Daniel Kral [this message]
2026-04-17 12:27 ` [PATCH ha-manager 1/7] sim: always limit the priority level to 4 characters Daniel Kral
2026-04-17 12:27 ` [PATCH ha-manager 2/7] consistently use correct priority levels for log calls Daniel Kral
2026-04-17 12:27 ` [PATCH ha-manager 3/7] sim: hardware: factor common service lock hash access in unlock_service Daniel Kral
2026-04-17 12:27 ` [PATCH ha-manager 4/7] use log with warning priority instead of warn where possible Daniel Kral
2026-04-17 12:27 ` [PATCH ha-manager 5/7] pve-ha-tester: capture and fail for unexpected perl warnings Daniel Kral
2026-04-17 12:27 ` [PATCH ha-manager 6/7] test: ha-tester: use consistent word casing for failed test messages Daniel Kral
2026-04-17 12:27 ` [PATCH ha-manager 7/7] test: ha-tester: use colorized diff for unexpected test log outputs Daniel Kral
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260417122728.330123-1-d.kral@proxmox.com \
--to=d.kral@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.