public inbox for kdevops@lists.linux.dev
 help / color / mirror / Atom feed
From: Daniel Gomez <da.gomez@kernel.org>
To: Chuck Lever <chuck.lever@oracle.com>,
	Luis Chamberlain <mcgrof@kernel.org>
Cc: kdevops@lists.linux.dev, Daniel Gomez <da.gomez@samsung.com>
Subject: Re: [PATCH 09/10] fstests: tmpfs: expunges: testing
Date: Thu, 26 Jun 2025 21:10:05 +0200	[thread overview]
Message-ID: <9655630e-5331-47f9-951d-8a48ef53a372@kernel.org> (raw)
In-Reply-To: <46577bbc-69c9-463c-ab1b-8acde1ec40a2@oracle.com>

On 16/06/2025 22.36, Chuck Lever wrote:
> On 6/16/25 4:24 PM, Daniel Gomez wrote:
>>
>>
>> On 16/06/2025 16.31, Chuck Lever wrote:
>>> On 6/16/25 6:41 AM, Daniel Gomez wrote:
>>>>
>>>> On 15/06/2025 18.18, Chuck Lever wrote:
>>>>> On 6/15/25 5:58 AM, Daniel Gomez wrote:
>>> generic/561 is testing file de-dup, which tmpfs does not implement.
>>>
>>> generic/561 looks for the dupremove utility on the test system to
>>> know whether to run the test. That's a poor check, say, if the test
>>> system is used for testing other file systems, or dupremove is installed
>>> by default.
>>
>> We need to fix that in kdevops and then figure out if generic/561 applies or
>> not.
>>
>>>
>>> Could be that 3b9f5fc7d7d8 ("common: call _require_scratch_dedupe from
>>> _require_scratch_duperemove") fixes that so that 561 no longer needs
>>> to be explicitly expunged for NFS and tmpfs.
>>>
>>>
>>
>> The above logs are from an fstests deployed by kdevops which already has that
>> commit.
>>
>> git -C /data/fstests log --oneline -1
>> 2cc8c822 (HEAD -> master, origin/master, origin/HEAD) fstests: btrfs: testcase
>> for sysfs chunk_size attribute validation
>>
>> So, I added duperemove package to the VM and run the test again:
>>
>> [   14.841609] run fstests fstestsstart/000 at 2025-06-16 18:17:35
>> [   16.365091] run fstests generic/561 at 2025-06-16 18:17:36
>> [   17.141361] run fstests fstestsdone/000 at 2025-06-16 18:17:37
>>
>> cat /data/fstests-install/xfstests/results/debian13-tmpfs-default/6.16.0-rc2/
>> tmpfs_default/generic/561.notrun
>> Dedupe not supported by scratch filesystem type: tmpfs
>>
>> I think the correct path is to add duperemove as fstests workflow dependency to
>> properly skip the test for tmpfs.
> 
> That sounds correct to me.

Added duperemove package to fstests workflow:
ac918af2fb3b fstests: debian: add duperemove dependency

https://github.com/linux-kdevops/kdevops/commit/ac918af2fb3bbd33c81281073f46f84025cffa5a

  parent reply	other threads:[~2025-06-26 19:10 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-15  9:58 [PATCH 00/10] Extend kdevops-ci to support more workflows Daniel Gomez
2025-06-15  9:58 ` [PATCH 01/10] .ci: blktests: add 1 section only targets Daniel Gomez
2025-06-15  9:58 ` [PATCH 02/10] defconfigs: add tmpfs support Daniel Gomez
2025-06-15  9:58 ` [PATCH 03/10] .ci: " Daniel Gomez
2025-06-15  9:58 ` [PATCH 04/10] defconfigs: blktests: add blktests_meta support Daniel Gomez
2025-06-15  9:58 ` [PATCH 05/10] gen_nodes: selftests: fix hosts names generation Daniel Gomez
2025-06-15  9:58 ` [PATCH 06/10] gen_hosts: " Daniel Gomez
2025-06-15  9:58 ` [PATCH 07/10] fstests: fix ansible range type error Daniel Gomez
2025-06-15  9:58 ` [PATCH 08/10] selftests: kmod: add timeout makefile parameter cli support Daniel Gomez
2025-06-15  9:58 ` [PATCH 09/10] fstests: tmpfs: expunges: testing Daniel Gomez
2025-06-15 16:18   ` Chuck Lever
2025-06-16 10:41     ` Daniel Gomez
2025-06-16 14:31       ` Chuck Lever
2025-06-16 20:24         ` Daniel Gomez
2025-06-16 20:36           ` Chuck Lever
2025-06-17  8:34             ` Daniel Gomez
2025-06-17 13:43               ` Chuck Lever
2025-06-21  7:47                 ` Daniel Gomez
2025-06-26 19:10             ` Daniel Gomez [this message]
2025-06-15  9:58 ` [PATCH 10/10] workflows: add support to change kdevops repo in guests via cli Daniel Gomez
2025-06-26 18:59 ` [PATCH 00/10] Extend kdevops-ci to support more workflows Daniel Gomez

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=9655630e-5331-47f9-951d-8a48ef53a372@kernel.org \
    --to=da.gomez@kernel.org \
    --cc=chuck.lever@oracle.com \
    --cc=da.gomez@samsung.com \
    --cc=kdevops@lists.linux.dev \
    --cc=mcgrof@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