From: Xiubo Li <xiubli@redhat.com>
To: fstests@vger.kernel.org
Cc: david@fromorbit.com, djwong@kernel.org,
ceph-devel@vger.kernel.org, vshankar@redhat.com,
zlang@redhat.com
Subject: Re: [PATCH] generic/075: no need to move the .fsxlog to the same directory
Date: Sun, 19 Mar 2023 14:31:19 +0800 [thread overview]
Message-ID: <c16a822c-1237-118b-ec3d-adf64289a7a5@redhat.com> (raw)
In-Reply-To: <20230301020730.92354-1-xiubli@redhat.com>
Ping.
What's the status of this patch ?
Thanks
- Xiubo
On 01/03/2023 10:07, xiubli@redhat.com wrote:
> From: Xiubo Li <xiubli@redhat.com>
>
> Actually it was trying to move the '075.$_n.fsxlog' from results
> directory to the same results directory.
>
> Fixes: https://tracker.ceph.com/issues/58834
> Signed-off-by: Xiubo Li <xiubli@redhat.com>
> ---
> tests/generic/075 | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/tests/generic/075 b/tests/generic/075
> index 9f24ad41..03a394a6 100755
> --- a/tests/generic/075
> +++ b/tests/generic/075
> @@ -57,7 +57,6 @@ _do_test()
> then
> echo " fsx ($_param) failed, $? - compare $seqres.$_n.{good,bad,fsxlog}"
> mv $out/$seq.$_n $seqres.$_n.full
> - mv "$RESULT_DIR"/$seq.$_n.fsxlog $seqres.$_n.fsxlog
> od -xAx $seqres.$_n.full > $seqres.$_n.bad
> od -xAx "$RESULT_DIR"/$seq.$_n.fsxgood > $seqres.$_n.good
> rm -f "$RESULT_DIR"/$seq.$_n.fsxgood
--
Best Regards,
Xiubo Li (李秀波)
Email: xiubli@redhat.com/xiubli@ibm.com
Slack: @Xiubo Li
next prev parent reply other threads:[~2023-03-19 6:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-01 2:07 [PATCH] generic/075: no need to move the .fsxlog to the same directory xiubli
2023-03-19 6:31 ` Xiubo Li [this message]
2023-03-20 14:37 ` Zorro Lang
2023-03-22 2:24 ` Xiubo Li
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=c16a822c-1237-118b-ec3d-adf64289a7a5@redhat.com \
--to=xiubli@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=david@fromorbit.com \
--cc=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=vshankar@redhat.com \
--cc=zlang@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;
as well as URLs for NNTP newsgroup(s).