You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I expect cdash_worker to process all submissions and keep running being available as needed.
Actual Behavior
Running docker start cdash_worker starts the container, makes it re-parse the same submission over again, at the end of which it terminates with exit code 12.
I am not sure how cdash_worker is expected to work. What does exit code 12 even mean?
UPD: I have tweaked docker-compose to restart cdash_worker on failure, and seemingly it "kind of works", but I am still not convinced that this is how it should work.
The text was updated successfully, but these errors were encountered:
Are there any error messages emitted while parsing the (seemingly) problematic submission before the cdash_worker container dies?
I am not sure that this particular submission is the reason for container termination. It seems to terminate at the end of parsing any submission. I actually worked around this by just setting restart:on-failure in docker-compose, although it is clearly a hack.
And I see no error messages in cdash_worker's logs, beyond it complaining that some files are not attributed to any subproject.
Bug report
Expected Behavior
I expect
cdash_worker
to process all submissions and keep running being available as needed.Actual Behavior
Running
docker start cdash_worker
starts the container, makes it re-parse the same submission over again, at the end of which it terminates with exit code 12.CDash Version
77410d7
Additional Information
I am not sure how
cdash_worker
is expected to work. What does exit code 12 even mean?UPD: I have tweaked docker-compose to restart
cdash_worker
on failure, and seemingly it "kind of works", but I am still not convinced that this is how it should work.The text was updated successfully, but these errors were encountered: