From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9]) by lore.proxmox.com (Postfix) with ESMTPS id 254C91FF14C for ; Fri, 15 May 2026 07:10:35 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 01B8BBFE7; Fri, 15 May 2026 07:10:35 +0200 (CEST) From: Thomas Lamprecht To: pve-devel@lists.proxmox.com, Daniel Kral Subject: applied: [PATCH ha-manager 0/7] some test logging output improvements Date: Fri, 15 May 2026 06:51:11 +0200 Message-ID: <177882064287.361203.6086384022125655272.b4-ty@b4> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260417122728.330123-1-d.kral@proxmox.com> References: <20260417122728.330123-1-d.kral@proxmox.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1778821794374 X-SPAM-LEVEL: Spam detection results: 0 AWL -0.122 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment KAM_LOTSOFHASH 0.25 Emails with lots of hash-like gibberish SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Message-ID-Hash: FNVTKBS2E33LG2UCLO3ZS65ZGG2WNEAF X-Message-ID-Hash: FNVTKBS2E33LG2UCLO3ZS65ZGG2WNEAF X-MailFrom: t.lamprecht@proxmox.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox VE development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: 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