From nobody Tue Apr 21 15:11:22 2026 X-Original-To: freebsd-testing@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4g0QmX4H21z6WqD3 for ; Tue, 21 Apr 2026 15:11:24 +0000 (UTC) (envelope-from markj@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R12" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4g0QmX3dZ4z3FN6 for ; Tue, 21 Apr 2026 15:11:24 +0000 (UTC) (envelope-from markj@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1776784284; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type; bh=NmPIvQ7FG3IkBEEIuTLjRm41Zo/XV6XIp23sAoUhBSo=; b=mcFoS/fjvqFEM2EXo2AS/KrQyU+2TDjh4uWGkBmbwstUrGZgSqjLX6hvc8cTI9+/69VeDI 1Bv0EIZ3QB8rP+/1+4NxIUrrIdcoDqlHBf2YDxLJQdhj11XUJYNijrsIREQbWRCh1qPcdx 94Ch9WyyXCTSdNLkeAocW+gQPYfmdnO7cz7OMiGxpK87yseaks4efayyYKWge/xzUasdi0 +6DgrTqbCpMX+0jLRuLm0qxg4jyYM7CXxQIZ9qe0KMMHpd5q5IYV8eYHLC7uWCFTEECjTb jDbM5ZcSNBuiNYljEjwpesR6YZKXxlSQsLsRABFvZnO1jyLWiwqbkfIGM8CWig== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1776784284; a=rsa-sha256; cv=none; b=WKtO1nob/am/Uv3cAYaaOYtcxF5jMHwoGIddsbKUIEDDzsOXIFpPZO2VnFNK6KrrzOrA9a L42Wq+G7PP/6pKX9isxmPIONKv/lHlri2RibQ9vGmGGcO5G4fMCzOaZwawaaqa6p0dL7cN Tun5EH+TOzdxm1r1t546NqLNJSTXGUUbFo7fbz4BPsdLBhMoes8De1g3UYqaihz8RH5Jr7 PGEUBSDYT8akcdjkrqYK61TwalNxM8Is0tEzBe3Etm95+MCJ25RFAgKhVYFltDzYFa6i7P 4uZ19dQ2OPK4WTCd9vGxxwDiv7PmRqj3bumt+3E/R4YZbNaHEm1DvTdLWLM9zg== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1776784284; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type; bh=NmPIvQ7FG3IkBEEIuTLjRm41Zo/XV6XIp23sAoUhBSo=; b=gTh6c6D2I2iBhJBxLFIKxBvRU6JxWgDHlOxyJPBNIRWhm9H+TWQ1tTguHXAaXjIzsR61bX xOv+G2syiWFkHbrKHo3u1g/LPjD+/lq4+CejmLRNcw3/yMayDADx08U18k/CbFwUBu+b95 L70jt2QWWPBqT4kXsLtNywIBg9J7DMUrO5JWX65hvzk6TasfO55m/4tkzcRWD3GrVU5Fzh 0rXFzXQWlA759xdKEuItEvhWPGKM1tQAFQGST/CuauZNytrV0isQq5c6kNnPV/YUhg8uig DAtOMPpq86mU90Dj69XuaipqoMd36yI22gexi846wAksunWXjqGN3qhwtkwiog== Received: from nuc (192-0-220-237.cpe.teksavvy.com [192.0.220.237]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) (Authenticated sender: markj) by smtp.freebsd.org (Postfix) with ESMTPSA id 4g0QmX2BKcz14rj for ; Tue, 21 Apr 2026 15:11:24 +0000 (UTC) (envelope-from markj@freebsd.org) Date: Tue, 21 Apr 2026 11:11:22 -0400 From: Mark Johnston To: freebsd-testing@freebsd.org Subject: pjdfstest integration Message-ID: List-Id: Testing List-Archive: https://lists.freebsd.org/archives/freebsd-testing List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-testing@freebsd.org Sender: owner-freebsd-testing@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi, I noticed that we install pjdfstest to /usr/tests/sys/pjdfstest, but: - it's not hooked up to the test suite, i.e., "kyua test -k /usr/tests/Kyuafile" doesn't run it, - contrib/pjdfstest doesn't seem to be updated regularly, - the configuration is hard-coded, i.e., I can't easily run it against a filesystem of my choice. How hard would it be to parameterize the tests so that we can run the tests again a list of filesystems? For each filesystem we'd have some little script that sets up some scratch space, creates an empty filesystem and points pjdfstest at it. In some cases we'd need the test runner to specify some additional variables, e.g., for p9fs you want the test runner to provide a share, as we currently only support the virtio transport. I'm not sure if kyua can pass variables to a TAP test, so the solution might be to wrap each pjdfstest run with an ATF test case which handles the setup. Is anyone interested in working on these things?