forked from kdave/xfstests
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
xfstests: Introduce a results directory
Currently each test gets it's sequence number from it's name. It separates this from the path via basename, and uses it for outputting full, notrun and other status/log files. Hence these end up in the top level directory. All these output files need to go somewhere other than the top level directory. Right now the check script is looking for them in the new test directories (e.g. for the notrun files), but it would be good to be able to separate the test source form the test output. Hence create an output directory which has a similar heirarchy to the test source directory. Create it on demand when we build the list of tests to run if it doesn't already exist. Change the high level check script to set up this variable appropriately for each test that is being run, and to use this new output directory for it's result files as well. The next commit will change all the tests themselves to use the new output directory. This is the first (small) step in being able to store test results in an external location for archival/data mining purposes. Signed-off-by: Dave Chinner <dchinner@redhat.com> Reviewed-by: Phil White <pwhite@sgi.com> [rjohnston@sgi.com rm whitespace and fix typos in commit message] Signed-off-by: Rich Johnston <rjohnston@sgi.com>
- Loading branch information
Dave Chinner
authored and
Rich Johnston
committed
Mar 27, 2013
1 parent
1f39e59
commit 1686f9a
Showing
9 changed files
with
152 additions
and
138 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.