This problem typically occurs, when a previous test has been interrupted (killed), for example with CTRL-C. A: TAT creates a file .testSession in the test directory of the module where the test is running.After finishing the test, this file gets deleted again. When interrupting a test, this file obviously gets not deleted. The file often contains information like "Do not execute prologue" (since the prologue was already executed in the current session, or since a user specifies this behaviour with special TAT configuration commands). Just delete the file .testSession and everything will be good again. REMARK :if the .testsession is there it is better to run first: tat -v -nc cleanEnv
because like that the epilogue is executed, and the processes activated with the prologue will be closed/shutdown etc... without doing kill or things like that. In general, every tat test can be split in three operations: - preparation phase (source of the source file, compile the software, run the prologue,...)
tat -v -nc makeEnv
tat -v -nc (in this case, the preparation phase is not repeated)
- clean-up phase (run the epilogue, clean-up the log directories, if any...)
tat -v -nc cleanEnv
|