Hi,
So there’s a test in HPS Java that initializes most of the steering files from trunk/steering-files to make sure that all the Driver classes exist and that the arguments map to set methods, and this test runs automatically with each Jenkins build.
The test is failing periodically because people are putting into the SVN steering files that don’t actually work. Usually this is due to missing set methods.
The solution here is…..don’t do this! If a steering file doesn’t work (e.g. it will not initialize successfully from the command line) but you still want it in SVN then you should put it into the sandbox. Then when it does work you can use ‘svn cp’ to move it to the steering-files module.
Thanks.
—Jeremy
########################################################################
Use REPLY-ALL to reply to list
To unsubscribe from the HPS-SOFTWARE list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=HPS-SOFTWARE&A=1
|