ATS - Automated Testing System - is an open-source, Python-based tool for automating the running of tests of an application across a broad range of high performance computers.
We used the floor version of ATS on LC and this leaves an atss.log file with every run (note the second 's'). I think this file is to debug scheduling issues. Can we get an option to only write out this file if we need to diagnose scheduling issues?
Reason is that with the longer runs on LC systems this file can get really large and takes up valuable space when moving results to the filesystem archive and to the html space for them to be searched. We have to add a removal for this file in automation scripts or we'll hit quotas quicker than expected.
We used the floor version of ATS on LC and this leaves an atss.log file with every run (note the second 's'). I think this file is to debug scheduling issues. Can we get an option to only write out this file if we need to diagnose scheduling issues? Reason is that with the longer runs on LC systems this file can get really large and takes up valuable space when moving results to the filesystem archive and to the html space for them to be searched. We have to add a removal for this file in automation scripts or we'll hit quotas quicker than expected.