Should be a relatively straightforward pull request.
Runner:
Error or not, run_job returns a dictionary called results with key successful
If no error has occurred (successful==True), then results will have a key called return_obj with the value being results of the job run (return_obj is what was originally returned instead of results)
Added error handling in run_job. If an error has occurred (successful==False), then results will have a key called error_message that will hold the actual error that took place when running the job.
Scheduler:
Added error handling + retry logic in runners_run_next_jobs. If the job finished unsuccessfully, add it to the end of the queue. If the job finished unsuccessfully more than max_tries (currently 3) times, ignore the job and don't add it back to the queue (might need an alternative for this)
max_tries is pulled from the configuration.ini
Other:
Edited tests/artifacts/configuration.ini and questions.csv to include max_tries.
This pull request serves to close #12
Should be a relatively straightforward pull request.
Runner:
run_jobreturns a dictionary calledresultswith keysuccessfulsuccessful==True), thenresultswill have a key calledreturn_objwith the value being results of the job run (return_objis what was originally returned instead ofresults)run_job. If an error has occurred (successful==False), thenresultswill have a key callederror_messagethat will hold the actual error that took place when running the job.Scheduler:
runners_run_next_jobs. If the job finished unsuccessfully, add it to the end of the queue. If the job finished unsuccessfully more thanmax_tries(currently 3) times, ignore the job and don't add it back to the queue (might need an alternative for this)max_triesis pulled from theconfiguration.iniOther:
tests/artifacts/configuration.iniandquestions.csvto includemax_tries.