All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: xfs-oss <xfs@oss.sgi.com>
Subject: xfstests tests not in the auto group; do we know why?
Date: Mon, 15 Dec 2008 23:01:10 -0600	[thread overview]
Message-ID: <49473616.1020307@sandeen.net> (raw)

Of the tests that are not in the auto group, do we know why they are not?

022: # Test out a level 0 dump/restore to a tape of a subdir
023: # To test xfsdump/restore to tape using a directory with
024: # Test out incremental dumps
025: # Test dump/restore using -m option (min strategy)
036: # Test xfsdump/restore minrmt to a remote IRIX tape
037: # Test xfsdump/restore minrmt to a remote linux tape
038: # Test xfsdump/restore to a remote linux tape
039: # Test xfsdump/restore to a remote IRIX tape
043: # Test out xfsdump/restore but rmv inventory prior to restore.
055: # Test xfsdump/restore to a remote IRIX tape using RMT user
059: # place holder for IRIX 059 test for xfsdump/xfsrestore multi streams
060: # place holder for IRIX 060 test for xfsdump/xfsrestore multi streams
064: # test multilevel dump and restores with hardlinks
071: # Exercise IO at large file offsets.
080: # rwtest (iogen|doio)
085: # To test log replay by shutdown of file system
086: # To test log replay with version 2 logs
087: # like 086 but want to create more/different kinds of metadata
098: # simple attr tests for EAs:
101: # This tests mkfs_udf with -s [SIZE] option.
102: # This tests mkfs_udf/mkudffs and the device detection code
104: # XFS online growfs-while-allocating tests (data subvol variant)
106: # Exercise basic xfs_quota functionality (user/group/project quota)
107: # Project quota.
108: # Simple quota accounting test for direct/buffered/mmap IO.
109: # ENOSPC deadlock case from Asano Masahiro.
110: # Incorrect dir2 freetab warning case from Masanori Tsuda.
111: # Infinite xfs_bulkstat bad-inode loop case from Roger Willcocks.
113: # aio-stress
114: # Test some parent ptr stuff
115: # Test out xfs_repair_ipaths
116: # Test out resetting of sb_qflags when mounting with no quotas
after having mounted with quotas.
118: # To test out pv#940675 crash in xfs_trans_brelse + quotas
119: # Leaking reservation space in the GRH
133: # Concurrent I/O to same file to ensure no deadlocks
136: # Test the attr2 code


udf tests are probably not auto out of principle? :)
071 fails/hangs on some platforms IIRC
104 hangs ...
"parent" requires code not committed(?)
"tape" group requires... tape so not auto?

# auto - tests to be run as part of nightly qa

I'm not sure what that means; is this group always supposed to pass?  If
so there are filestreams tests that don't, for example.  Maybe "tests
that don't hang?"

I wonder if it'd be worth documenting this a bit, and have a group which
should always run & pass on the core architectures.  (and for those that
don't pass, do a bit of documentation on why they don't?)

-Eric

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

             reply	other threads:[~2008-12-16  5:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-16  5:01 Eric Sandeen [this message]
2008-12-19 21:44 ` xfstests tests not in the auto group; do we know why? Christoph Hellwig
2008-12-20  5:10   ` Dave Chinner
2008-12-20  5:50     ` Eric Sandeen
2008-12-20  5:52   ` Eric Sandeen
2008-12-20  6:01   ` Eric Sandeen

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=49473616.1020307@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=xfs@oss.sgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.