From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) by lore.proxmox.com (Postfix) with ESMTPS id 95E2C1FF187 for ; Fri, 2 Jan 2026 21:32:40 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id B7C851079B; Fri, 2 Jan 2026 21:33:51 +0100 (CET) From: Stoiko Ivanov To: pmg-devel@lists.proxmox.com Date: Fri, 2 Jan 2026 21:31:58 +0100 Message-ID: <20260102203253.28218-1-s.ivanov@proxmox.com> X-Mailer: git-send-email 2.47.3 MIME-Version: 1.0 X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1767385966340 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.070 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 RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_RPBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_SAFE_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Subject: [pmg-devel] [PATCH pmg-api 0/3] enable building with sbuild, by refactoring tests X-BeenThere: pmg-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox Mail Gateway development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: pmg-devel-bounces@lists.proxmox.com Sender: "pmg-devel" Building pmg-api in sbuild is currently not possible, due to 2 issues: * the format_date_header tests in test_util.pl implicitly assume a CET/CEST timezone (patch 1/3) * most other tests in pmg-api are integration-tests - they create postgres databases, dump them, start services, and expect syslog to work. this is changed by skipping the tests conditionally (with the condition evaluating to true in an sbuild environment) I considered reworking the tests on the database to output a stable text file for comparison (the output of `pmgdb dump` would work), but the RuleDB code is tightly coupled to writing to the database - changing that would amount to a far larger refactoring of pmg-api. So instead leave the default build calls most of us working with pmg-api as they are and skip the tests in sbuild (or by setting an environment variable). checking out autopkgtests for the other tests is probably a good idea - but should not prevent us from having a working sbuild target for pmg-api. Stoiko Ivanov (3): tests: test_utils: do not rely on system timezone tests: make test nature explicit tests: conditionally skip integration tests src/tests/Makefile | 32 +++++++++++++++++++------------- src/tests/test_utils.pl | 5 ++++- 2 files changed, 23 insertions(+), 14 deletions(-) -- 2.47.3 _______________________________________________ pmg-devel mailing list pmg-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pmg-devel