Missing module label in exception message
One of my Mu2e colleagues, Dave Brown ( email@example.com), reports a problem in the information produced when an art module throws an exception - see below. The exception message does not contain the module label that was active when the exception occurred.
We are using art v2_06_02 and plan to upgrade in the next day or so to v2_07_03. We will not upgrade to art v2_08_02 for a while because our prototype online system is not yet ready for that.
I'm trying to debug some new configuration with the head of Offline,
and unfortunately I find the 'module' information is missing from the
art exception printout as shown below (no module is listed after
'cet::exception going through module'). This makes it hard to debug.
Has anyone else noticed this?
cet::exception caught in art ---- EventProcessorFailure BEGIN An exception occurred during current event processing ---- EventProcessorFailure BEGIN An exception occurred during current event processing ---- ScheduleExecutionFailure BEGIN ProcessingStopped. ---- ProductNotFound BEGIN getByLabel: Found zero products matching all criteria Looking for type: std::vector<mu2e::MVAStruct<mu2e::TrkQualDetail> > Looking for module label: KFFDeM Looking for productInstanceName: cet::exception going through module ---- ProductNotFound END Exception going through path end_path ---- ScheduleExecutionFailure END ---- EventProcessorFailure END ---- EventProcessorFailure END %MSG Art has completed and will exit with status 18.