Project

General

Profile

Bug #20386

run_demo (and presumably just_do_it) should not continue when there is a configuration error

Added by Kurt Biery about 2 years ago. Updated about 2 years ago.

Status:
New
Priority:
Low
Assignee:
-
Category:
-
Target version:
-
Start date:
07/21/2018
Due date:
% Done:

0%

Estimated time:
Experiment:
-
Co-Assignees:
Duration:

Description

I just did a run with run_dumo.sh in which the following error was reported:

Error / ArtException
21-Jul-2018 16:34:23 CDT
mu2edaq01.fnal.gov (131.225.80.173)
UDPMessage 2 / PID 12449
art / Early / JobSetup
cet::exception caught in art
---- Configuration BEGIN
The following were encountered while processing the module configurations:
ERROR: Configuration of module with label randomDelay encountered the following error:
---- Can't find key BEGIN
module_type
---- Can't find key END

---- Configuration END

Despite this error, the scripts continued to the running state.

When there is a configuration error, the system should stop at that point and alert the user.

History

#1 Updated by Kurt Biery about 2 years ago

  • Priority changed from Normal to Low

Also available in: Atom PDF