\Models\ folder in the main folder has sample files. I believe these are the sample files that get downloaded with the executable. Some of these files are old and out-of-date and need to be upgraded over time.
For future builds, this folder needs to be alidated\ as part of the build process, as in they need to at least load up and run successfully. Suggest using the new \job\ command in trunk to run it during the build process. If any of the files fail, then the build should be halted (or a message sent, whichever is easiest to implement).
nikhilgupta10 imported these comments from Sourceforge:
The user dchassin does not exist anymore. Therefore assigning this to afisher1.
owner changed from natet to jcfuller
status changed from new to assigned
,
Description has changed:
Diff:
Milestone: Version 3.0 RC 1 --> Version 3.2 RC1
Resolution: --> none
Component: Unknown --> none
Priority: minor --> critical
,
Andy, I seemed to believe we took care of this by copying them into individual test folders. Maybe we can also just add an autotest folder to the models folder?,
\Models\ folder in the main folder has sample files. I believe these are the sample files that get downloaded with the executable. Some of these files are old and out-of-date and need to be upgraded over time.
For future builds, this folder needs to be alidated\ as part of the build process, as in they need to at least load up and run successfully. Suggest using the new \job\ command in trunk to run it during the build process. If any of the files fail, then the build should be halted (or a message sent, whichever is easiest to implement).
,