public inbox for fstests@vger.kernel.org
 help / color / mirror / Atom feed
From: Zorro Lang <zlang@redhat.com>
To: fstests@vger.kernel.org
Subject: [PATCH v3 2/2] xfs/068: new fsstress operation breaks xfsrestore output
Date: Sat, 19 Jan 2019 10:42:58 +0800	[thread overview]
Message-ID: <20190119024258.6864-2-zlang@redhat.com> (raw)
In-Reply-To: <20190119024258.6864-1-zlang@redhat.com>

After fsstress has new operation, xfs/068 has different dump output,
so change the expected number of files and directories.

Signed-off-by: Zorro Lang <zlang@redhat.com>
---
 tests/xfs/068.out | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/tests/xfs/068.out b/tests/xfs/068.out
index fa3a5523..f9ec37b8 100644
--- a/tests/xfs/068.out
+++ b/tests/xfs/068.out
@@ -22,7 +22,7 @@ xfsrestore: session id: ID
 xfsrestore: media ID: ID
 xfsrestore: searching media for directory dump
 xfsrestore: reading directories
-xfsrestore: 383 directories and 1335 entries processed
+xfsrestore: 416 directories and 1373 entries processed
 xfsrestore: directory post-processing
 xfsrestore: restoring non-directory files
 xfsrestore: restore complete: SECS seconds elapsed
-- 
2.17.2

  reply	other threads:[~2019-01-19  2:43 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-19  2:42 [PATCH v3 1/2] fsstress: add splice support Zorro Lang
2019-01-19  2:42 ` Zorro Lang [this message]
2019-01-21 22:44   ` [PATCH v3 2/2] xfs/068: new fsstress operation breaks xfsrestore output Dave Chinner
2019-01-22  3:33     ` Amir Goldstein
2019-01-22  4:58       ` Zorro Lang
2019-01-22 22:22         ` Dave Chinner
2019-01-23  3:44           ` Zorro Lang
2019-01-23  4:12             ` Dave Chinner
2019-01-23  7:35             ` Amir Goldstein
2019-01-23  8:41               ` Zorro Lang
2019-01-23  8:59                 ` Amir Goldstein
2019-01-23 22:06               ` Dave Chinner
2019-01-24  9:28                 ` Amir Goldstein

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=20190119024258.6864-2-zlang@redhat.com \
    --to=zlang@redhat.com \
    --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