rabbitmq.out is not found by start_model_runs, job hangs
istfer opened this issue · comments
Bug Description
With containers: Has someone else encountered a problem where job is submitted to the queue, actually runs through and finishes successfully, writes out rabbitmq.out
to file.path(settings$rundir, run_id_string)
(e.g. as in here) but then workflow keeps hanging because start_model_runs looks for it under modeloutdir folder (not in run
folder where it is written).
Before it was indeed looking for rabbitmq.out
under run
folder, @Aariq you seem to have made a change related to this relatively recently. In my case I'm running model locally, could it be that when you made the change you only modified and tested for the !is_local
case?
Or am I missing something else? Why could the rabbitmq.out
be appearing only in rundir
in my case if it's supposed to be under modeloutdir?
Expected behavior
rabbitmq.out
is either copied over to the out
directory or start_model_runs
looks for it under run
folder.