FS/XFS testing framework
 help / color / mirror / Atom feed
From: Zorro Lang <zlang@redhat.com>
To: Pavel Reichl <preichl@redhat.com>
Cc: fstests@vger.kernel.org
Subject: Re: [PATCH 3/4] generic: cleanup test files
Date: Fri, 23 Sep 2022 01:58:28 +0800	[thread overview]
Message-ID: <20220922175828.fxsd4kkdzaihruhk@zlang-mailbox> (raw)
In-Reply-To: <079f6725-1f75-24dc-c233-4544c242b30b@redhat.com>

On Thu, Sep 22, 2022 at 07:05:57PM +0200, Pavel Reichl wrote:
> 
> > I'm wondering two questions:
> > 1) If these cases all use $TEST_DIR/seek_sanity_testfile, and don't really
> >     remove these seek_sanity_testfile* files, will them affect each testing
> >     result? Can we set BASE_TEST_FILE=$TEST_DIR/seek_sanity_testfile_$seq
> >     at least, to avoid they use same files?
> I'm happy to try to implement this idea.

If you need to remove them in cleanup, then the name won't conflict :)

> 


  reply	other threads:[~2022-09-22 17:58 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-22 13:48 [PATCH 1/4] common: Fix file leak in _get_max_file_size Pavel Reichl
2022-09-22 13:48 ` [PATCH 2/4] g/299: speed up the test Pavel Reichl
2022-09-22 15:16   ` Zorro Lang
2022-09-22 13:48 ` [PATCH 3/4] generic: cleanup test files Pavel Reichl
2022-09-22 14:36   ` Zorro Lang
     [not found]     ` <91ec6d59-5014-2e3e-8e80-aac162b8ffc1@redhat.com>
2022-09-22 15:08       ` Zorro Lang
2022-09-22 17:05     ` Pavel Reichl
2022-09-22 17:58       ` Zorro Lang [this message]
2022-09-22 13:48 ` [PATCH 4/4] g/394: clean up " Pavel Reichl
2022-09-22 15:04   ` Zorro Lang
2022-09-22 14:46 ` [PATCH 1/4] common: Fix file leak in _get_max_file_size Zorro Lang
2022-09-22 14:51   ` Pavel Reichl
2022-09-23  3:31 ` Eric Biggers
2022-09-23  5:04   ` Zorro Lang

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=20220922175828.fxsd4kkdzaihruhk@zlang-mailbox \
    --to=zlang@redhat.com \
    --cc=fstests@vger.kernel.org \
    --cc=preichl@redhat.com \
    /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