The current behavior of the software is that if there is a folder non containing a lab.conf it crashes stopping all the process.
This is an unwanted behavior since the next start will be from scratch. If I'm passing over many directories, it will take a lot of time to process them from the beginning.
I see here two possible solutions if there is no lab.conf:
Just skip the directory, catch the exception, write something in stdout, and pass over.
Let the software crash, but implement a --resume option that avoid testing a directory if inside that directory there is already a test_results directory
lorenzo93
commented
9 months ago
The current behavior of the software is that if there is a folder non containing a
lab.confit crashes stopping all the process. This is an unwanted behavior since the next start will be from scratch. If I'm passing over many directories, it will take a lot of time to process them from the beginning.I see here two possible solutions if there is no
lab.conf:--resumeoption that avoid testing a directory if inside that directory there is already atest_resultsdirectory