Handle error the same way for all algorithm types on execution
Currently sequential and autonomous algorithms are not treating errors happening in the process method the same way. This result in missing information coming back up through beat/beat.core>
This patch fixes this and also ensure that the outputs are properly closed.
Fixes beat.core#98 (closed)
Merge request reports
Activity
changed milestone to %Soft loops
cc @andre.anjos
Note that in order to test that with the Docker executor, you need to either:
- update the images with a new release of beat/beat.backend/python> containing this change
- modify the docker executor to add a volume mapping the beat.backend.python sources at the right place in the container.
That's one of the issue we have with the combo beat/beat.core> and beat/beat.backend.python>: the tests are distributed between both repositories.
In the case of this one, the error handling that interests you is in fact done at the beat/beat.core> level. But for you to see them, I have to first publish new images to the CI so both the local and docker execution can be validated with the changes done here.
It's ok if test are in beat/beat.core> but I still would like to see them in beat.core!123 (merged)
I have added additional tests and they are ready to be pushed however, as long as the test images are not updated, they won't pass for the Docker related part.
Edited by Samuel GAISTmentioned in commit 26a01773
mentioned in issue beat.core#99 (closed)