Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*xfstests\s+should\s+still\s+make\s+xfs\s+as\s+default\?\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*xfstests\s+should\s+still\s+make\s+xfs\s+as\s+default\?\s*$/: 3 ]

Total 3 documents matching your query.

1. xfstests should still make xfs as default? (score: 1): Author: Carlos Maiolino <cmaiolino@xxxxxxxxxx>; Date: Wed, 27 Mar 2013 17:32:32 -0300; Hi, working on xfstests after its new directory structures I noticed we should use now something like: ./check xfs/<test> to run some tests, IMHO this is not intuitive and I was working on a patch to; /archives/xfs/2013-03/msg00777.html (7,194 bytes)
2. Re: xfstests should still make xfs as default? (score: 1): Author: Dave Chinner <david@xxxxxxxxxxxxx>; Date: Tue, 9 Apr 2013 09:07:34 +1000; What do you do with duplicate test names? The main reason that the interface changed was to keep the changes to the test harness down to a minimum as it was just moving tests around. All that code ne; /archives/xfs/2013-04/msg00148.html (8,574 bytes)
3. Re: xfstests should still make xfs as default? (score: 1): Author: Carlos Maiolino <cmaiolino@xxxxxxxxxx>; Date: Tue, 9 Apr 2013 11:03:59 -0300; Hi, this makes sense to me Dave, thanks to the explanation. We have some documentation which says xfstests will run tests for a xfs filesystem by default if no other fstype is specified, I'll change; /archives/xfs/2013-04/msg00169.html (10,186 bytes)

Current List: 1 - 3
Page: [1]