very uninformative diagnostic
Below is a complete output from an art run. The error message gives no clue on where the problem is.
This was for a non-trivial job setup with multiple paths, filters, output modules...
And with configuration spread out over several fcl files.
I could not find the mistake until I ran the program under
gdb and walked up the stack frame to figure out the offender.
Turns out, there was a typo in a line that set the output file name
Please provide a more informative error message.
%MSG-i MF_INIT_OK: mu2e 19-Dec-2013 13:23:46 CST JobSetup Messagelogger initialization complete. %MSG %MSG-s ArtException: mu2e 19-Dec-2013 13:23:48 CST JobSetup cet::exception caught in art ---- Can't find key BEGIN module_type ---- Can't find key END %MSG Art has completed and will exit with status 8001. Command exited with non-zero status 65