From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id 7AB7370AB3 for ; Mon, 6 Sep 2021 17:00:28 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 714AF1311E for ; Mon, 6 Sep 2021 17:00:28 +0200 (CEST) Received: from proxmox-new.maurer-it.com (proxmox-new.maurer-it.com [94.136.29.106]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS id BE6561310B for ; Mon, 6 Sep 2021 17:00:27 +0200 (CEST) Received: from proxmox-new.maurer-it.com (localhost.localdomain [127.0.0.1]) by proxmox-new.maurer-it.com (Proxmox) with ESMTP id 83FB5445C8 for ; Mon, 6 Sep 2021 17:00:27 +0200 (CEST) From: Dominik Csapak To: pbs-devel@lists.proxmox.com Date: Mon, 6 Sep 2021 17:00:26 +0200 Message-Id: <20210906150026.1551456-2-d.csapak@proxmox.com> X-Mailer: git-send-email 2.30.2 In-Reply-To: <20210906150026.1551456-1-d.csapak@proxmox.com> References: <20210906150026.1551456-1-d.csapak@proxmox.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-SPAM-LEVEL: Spam detection results: 0 AWL 0.429 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Subject: [pbs-devel] [PATCH proxmox-backup v2 2/2] tape/inventory: fix the tape tests as user, by mocking the lock X-BeenThere: pbs-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox Backup Server development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Sep 2021 15:00:28 -0000 locking during the tests as regular user failed because we try to chown to the backup user (which is not always possible). Instead, do not lock at all, by implementing 'open_backup_lockfile' with 'create_mocked_lock' Signed-off-by: Dominik Csapak --- changes from v1: * put unsafe block around 'create_mocked_lock' src/tape/inventory.rs | 15 ++++++++++++++- 1 file changed, 14 insertions(+), 1 deletion(-) diff --git a/src/tape/inventory.rs b/src/tape/inventory.rs index d56b2144..93d72057 100644 --- a/src/tape/inventory.rs +++ b/src/tape/inventory.rs @@ -40,7 +40,20 @@ use proxmox::tools::{ }; use pbs_systemd::time::compute_next_event; -use pbs_config::{open_backup_lockfile, BackupLockGuard}; +use pbs_config::BackupLockGuard; + +#[cfg(not(test))] +use pbs_config::open_backup_lockfile; + +#[cfg(test)] +fn open_backup_lockfile>( + _path: P, + _timeout: Option, + _exclusive: bool, +) -> Result { + Ok(unsafe { pbs_config::create_mocked_lock() }) +} + use crate::{ api2::types::{ -- 2.30.2