This causes a very weird XFS failure in test 117 for me. While it obviously is an xfs bug that you uncovered (good!) I'm a bit worried about simply enabling operations in existing tests. Alex, Eric,
Ohh. i've got what your are talking about. We can not add new ops for tests there seed is passed explicitly. And yes i've braked this, but this is because such frozen tests was written in not determi
One argument for adding new ops to existing tests is that it makes the run time of the entire test suite take longer. A QA pass is already taking quite a while, and it would be nice if we could keep
Yes, but regression test with explicit seed option should be preserved. Number of such test is not too big, so it is reasonable to hardcode set of operations in such tests and let all others use new
On Thu, 03 Nov 2011 13:34:41 +0400, Dmitry Monakhov <dmonakhov@xxxxxxxxxx> wrote: i've stuck immediately on first test ;(. on my kernel 107'th test always failed (commit: 73a57c642cdfa660 "1.1.0 rele
That's not what I was talking about. Of course there should be a way to run a regression test with an explicit seed option (although in general I think a specific test in xfstests should by default u