[
https://issues.apache.org/jira/browse/DERBY-5259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13044722#comment-13044722
]
Kristian Waagan commented on DERBY-5259:
----------------------------------------
Do you know if this is true for all of the files that are saved / written to in
the fail directory?
The file containing the error stack trace is supposed to be appended, so if it
only contains one trace maybe the test is purging the directory?
One scheme is to append date_time[_counter] to the files. The only downside is
that this may eat up a lot of disk space, due to copies of the database, in
some rare cases (i.e. you test a bad patch that causes most of the tests to
fail).
> If an upgrade test fails for multiple versions the fail directory output is
> not preserved for all versions
> ----------------------------------------------------------------------------------------------------------
>
> Key: DERBY-5259
> URL: https://issues.apache.org/jira/browse/DERBY-5259
> Project: Derby
> Issue Type: Bug
> Components: Test
> Affects Versions: 10.9.0.0
> Reporter: Kathey Marsden
> Priority: Minor
>
> If JUnit tests fail, the failure infomation including stack trace, database
> and derby.log are saved to a directory:
> fail/<framework>/<TestClass>/fixture
> For the upgrade tests, fixtures are run many times for multiple versions. If
> one of the tests fails in more than one version only the output of one of the
> failures will be preserved. It would be nice to save them all.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
