On Sun, Feb 23, 2025 at 08:27:43PM +0800, Zorro Lang wrote: > Hi all, > > The for-next branch of the xfstests repository at: > > git://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git > > has just been updated and tagged as v2025.02.23 release. > > Release Notes: > 1) There's not new test cases in this release, this's a release for bug fixes > particularly. > 2) Reiserfs part is removed from fstests. > 3) ltp/growfiles is removed too, I think no one needs it. > > I can't list all updates at here, more details please refer to below. > Thanks for all these contributions! > > Thanks, > Zorro > > The new head of the for-next branch is commit: > > 5b56a2d88819 fstests: remove reiserfs support > > New commits: > > Christoph Hellwig (1): > [04d0cf3f8909] generic/370: don't exclude XFS > > Darrick J. Wong (35): > [cc379f50f3bd] generic/476: fix fsstress process management > [ab459c67c5e0] metadump: make non-local function variables more obvious > [f428edcec2a2] metadump: fix cleanup for v1 metadump testing > [e68a92376165] generic/019: don't fail if fio crashes while shutting down > [48a3731b50ba] fuzzy: do not set _FSSTRESS_PID when exercising fsx > [543795bf67f2] common/rc: revert recursive unmount in _clear_mount_stack > [777732b27e62] common/dump: don't replace pids arbitrarily > [81f28acda2f2] common/populate: correct the parent pointer name creation formulae > [9b177d92dc65] generic/759,760: fix MADV_COLLAPSE detection and inclusion > [241c1c787e5b] generic/759,760: skip test if we can't set up a hugepage for IO > [77548e6066fd] common/rc: create a wrapper for the su command > [ac2d48f81094] fuzzy: kill subprocesses with SIGPIPE, not SIGINT > [c71349150d34] common/rc: hoist pkill to a helper function > [91d2880aa029] tools: add a Makefile > [88d60f434bd9] common: fix pkill by running test program in a separate session > [247ab01fa227] check: run tests in a private pid/mount namespace > [949bdf8eae31] check: deprecate using process sessions to isolate test instances I'm using a setup with a minimal VM system without systemd and such and dedicate the whole machine to one instance. I'm not interested in the check-parallel updates and test case separation. All fine if it is supported and lets me continue using single instance. But as I read it and the deprecation it's not going to be the supported use case. After last week update of fstests 100% of cases failed in the test setup (_seq_run). My workaround is to simply disable it by check: HAVE_PRIVATENS= HAVE_SYSTEMD_SCOPES= so I don't have to debug changes to the detection of the scope and namespaces and after each for-next update. I understand that with a custom system setup I'm on my own but until recently things have been fine but now after each update either test cases fail or the whole test infrastructure does not work. It's not just me who observes that. It seems that BTRFS is not tested before release as thoroughly as other filesystems (probably just XFS).
