From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Daniel Kral <d.kral@proxmox.com>
Subject: applied: [PATCH ha-manager 0/7] some test logging output improvements
Date: Fri, 15 May 2026 06:51:11 +0200 [thread overview]
Message-ID: <177882064287.361203.6086384022125655272.b4-ty@b4> (raw)
In-Reply-To: <20260417122728.330123-1-d.kral@proxmox.com>
On Fri, 17 Apr 2026 14:27:15 +0200, Daniel Kral wrote:
> 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
>
> [...]
Applied, thanks!
[1/7] sim: always limit the priority level to 4 characters
commit: fec966f6e41e94a5199ec9e8fae7b7bb7940c9f9
[2/7] consistently use correct priority levels for log calls
commit: 6d5bdd918edc0077293bbc5a04d1e6b79afa1857
[3/7] sim: hardware: factor common service lock hash access in unlock_service
commit: 5c3cccaec3b24e62f220d1e6187b0fff44ee19f7
[4/7] use log with warning priority instead of warn where possible
commit: 60f8a400f12f320be57607dc41480581c7597214
[5/7] pve-ha-tester: capture and fail for unexpected perl warnings
commit: a8962c91014e958f0660e701fd1b2fa0aee4556a
[6/7] test: ha-tester: use consistent word casing for failed test messages
commit: 9b2dc0b822ff9a3059eec82e663d05f0be84079f
[7/7] test: ha-tester: use colorized diff for unexpected test log outputs
commit: b9709671aa0fad928044e1530d62745484a2b15b
prev parent reply other threads:[~2026-05-15 5:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-17 12:27 [PATCH ha-manager 0/7] some test logging output improvements Daniel Kral
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
2026-05-15 4:51 ` Thomas Lamprecht [this message]
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=177882064287.361203.6086384022125655272.b4-ty@b4 \
--to=t.lamprecht@proxmox.com \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox