From: Zorro Lang <zlang@kernel.org>
To: fstests@vger.kernel.org
Subject: [ANNOUNCE] fstests: for-next branch updated to bb04d577435d
Date: Sun, 01 May 2022 03:09:13 +0800 [thread overview]
Message-ID: <20220430190921.7BC56C385A7@smtp.kernel.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 8296 bytes --]
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 for a v2022.05.01 release.
This's the first time for me to release a new fstests version. I just got the
maintaining job from Eryu. Thanks Eryu, for his long time contribution and help
to fstests project!
As you can see, I just updated on a new branch. From now on, I make two changes
for later fstests release:
1) A new offical branch -- for-next
You might notice that fstests has two old enough remote branches named
origin/mmap-truncate and origin/upstream-queue, it's been ~10 years we never
touched these two branches, so I've removed them after talking with other
maintainers.
After remove these two branches, I create a new 'for-next' branch. I'll merge
and push new patches to "for-next" branch at first, and leave one (maybe more,
sometimes) week "Soak period" to the for-next release. I'll test new patches
before push them, but it's hard for me to test all things which fstests support.
So I decide to leave about one week to let other users use it. Welcome more
using and testing on this branch, and find big issues as soon as better. That's
what the for-next branch aims to.
If there's big regression on for-next branch, I will fix on for-next branch and
push it next time. If there's not big regression issue, I'll merge for-next
to master and push master, then update and push new for-next release too.
For example, as below, this week I pushed for-next R1', next time I'll push
for-next R2' and master R1. Next next time will be for-next R3' and master R2,
and so on... If there's a big regression issue on R3', I will try to fix it in
next R4', and master branch has to wait one more week to merge and push R4.
(fix regression)
for-next ----> R1' ----> R2' -----> R3' -----------------> R4' -----> R5'
^ | | |
| (fork) | (merge) | (merge) | (merge)
| V V V
master ----> R1 -----> R2 -----------------------------> R4
(orig)
So if you prefer latest fstests, or contributing fstests, please use for-next.
Or you can keep using master branch.
And of course, there might be some topic(/unstable/temporary) branches appear,
those branches might be rebase / reset / delete ... so don't rely on them too
much.
2) Push signed version tag for new release.
I start to push singed (by me) version tag each time I push to for-next branch.
The version format is "v$(date +%Y.%m.%d)", e.g. "v2022.05.01".
Thanks,
Zorro
The new head of the for-next branch is commit:
bb04d577435d fstests: add some missing _require_loop's
New commits (N=New case, U=Update, D=Delete case):
Christian Brauner (1):
(N) [31c01ce18f73] generic: add test for tmpfs POSIX ACLs
Chung-Chiang Cheng (1):
(N) [987700db300d] fstests: btrfs: test setting compression via xattr on nodatacow files
Darrick J. Wong (4):
(U) [af8aeeea48d0] xfs/019: fix golden output for files created in setgid dir
(U) [ad5f89ef3013] generic/019: fix incorrect unset statements
(N) [7f27a290aca8] xfs: make sure syncfs(2) passes back super_operations.sync_fs errors
(N) [e81417a0964a] generic: ensure we drop suid after fallocate
Eric Sandeen (2):
(N) [80a82f6926fa] xfs: test xfsdump when an inode < root inode is present
(D) [7753e08d22e9] fstests: remove xfs/144
Jan Kara (2):
(U) [858a19c5e9b0] idmapped_mounts: Prepare for support for more features
(U) [95c10ab90c28] generic/633: Avoid failure without CONFIG_USER_NS
Josef Bacik (1):
(U) [bb04d577435d] fstests: add some missing _require_loop's
Murphy Zhou (1):
(U) [0fd8e26141f5] chown: fix ownership format string
Rishabh Dave (1):
(U) [1dac95cb0d6e] cephfs: add ceph-fuse suport for ceph-fuse
Theodore Ts'o (1):
(U) [5528f7843b1a] generic/681, generic/682: add debugging information to $seqreq.full
Yang Xu (1):
(U) [298f60c81a93] generic/673: Add separate sgid stripping sub-tests
Zorro Lang (2):
(U) [380ee98d92e6] fstests: remove _wipe_fs from dump testing entirely
(U) [ab47e281b70f] fsstress: remove ALLOCSP and FREESP operations entirely
Code Diffstat:
common/config | 2 +
common/dump | 23 +--
common/rc | 47 +++++--
ltp/fsstress.c | 117 ----------------
src/idmapped-mounts/idmapped-mounts.c | 257 +++++++++++++++++++++++++++-------
tests/btrfs/012 | 1 +
tests/btrfs/264 | 91 ++++++++++++
tests/btrfs/264.out | 11 ++
tests/generic/019 | 4 +-
tests/generic/070 | 2 -
tests/generic/099 | 4 +-
tests/generic/237 | 2 +-
tests/generic/318 | 2 +-
tests/generic/380 | 2 +-
tests/generic/597 | 6 +-
tests/generic/598 | 6 +-
tests/generic/648 | 1 +
tests/generic/673 | 37 ++++-
tests/generic/673.out | 24 ++++
tests/generic/681 | 4 +
tests/generic/682 | 4 +
tests/generic/683 | 127 +++++++++++++++++
tests/generic/683.out | 33 +++++
tests/generic/684 | 127 +++++++++++++++++
tests/generic/684.out | 33 +++++
tests/generic/685 | 127 +++++++++++++++++
tests/generic/685.out | 33 +++++
tests/generic/686 | 127 +++++++++++++++++
tests/generic/686.out | 33 +++++
tests/generic/687 | 127 +++++++++++++++++
tests/generic/687.out | 33 +++++
tests/generic/688 | 77 ++++++++++
tests/generic/688.out | 13 ++
tests/generic/689 | 33 +++++
tests/generic/689.out | 2 +
tests/xfs/019 | 3 +-
tests/xfs/019.out | 2 +-
tests/xfs/022 | 3 +
tests/xfs/023 | 3 +
tests/xfs/024 | 3 +
tests/xfs/025 | 3 +
tests/xfs/026 | 3 +
tests/xfs/027 | 3 +
tests/xfs/028 | 7 +-
tests/xfs/035 | 7 +
tests/xfs/036 | 3 +
tests/xfs/037 | 3 +
tests/xfs/038 | 3 +
tests/xfs/039 | 3 +
tests/xfs/043 | 5 +-
tests/xfs/046 | 3 +
tests/xfs/047 | 7 +-
tests/xfs/055 | 4 +
tests/xfs/056 | 3 +
tests/xfs/059 | 3 +
tests/xfs/060 | 3 +
tests/xfs/061 | 3 +
tests/xfs/063 | 3 +
tests/xfs/064 | 3 +
tests/xfs/065 | 3 +-
tests/xfs/066 | 3 +
tests/xfs/068 | 3 +
tests/xfs/144 | 128 -----------------
tests/xfs/144.out | 151 --------------------
tests/xfs/266 | 3 +
tests/xfs/267 | 4 +-
tests/xfs/268 | 4 +-
tests/xfs/281 | 4 +-
tests/xfs/282 | 4 +-
tests/xfs/283 | 4 +-
tests/xfs/296 | 4 +-
tests/xfs/301 | 2 +
tests/xfs/302 | 3 +-
tests/xfs/545 | 62 ++++++++
tests/xfs/545.out | 47 +++++++
tests/xfs/546 | 43 ++++++
tests/xfs/546.out | 2 +
77 files changed, 1611 insertions(+), 521 deletions(-)
--
Zorro Lang
zlang@kernel.org
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
reply other threads:[~2022-04-30 19:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220430190921.7BC56C385A7@smtp.kernel.org \
--to=zlang@kernel.org \
--cc=fstests@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox