Project

General

Profile

Feature #23555

Test status of components and catch/throw relevant exceptions

Added by Iker de Icaza Astiz 3 months ago. Updated 3 months ago.

Status:
New
Priority:
Low
Assignee:
Jose Ignacio Crespo Anadon
Start date:
11/06/2019
Due date:
% Done:

0%

Estimated time:
Co-Assignees:
Kathryn Sutton
Duration:

Description

There's a lack of information on the TPC board reader from anomalous processes.

Case in point: currently the code doesn't test if the WinDriver is loaded properly and crashes on the start transition with an "unknown exception".

History

#1 Updated by Jose Ignacio Crespo Anadon 3 months ago

  • Priority changed from Normal to Low

There are plans to improve the logging and exception management, but they have lower priority than other more urgent tasks.

We should not be checking if WinDriver is loaded every time we start a run, it should be loaded and checked when the servers boot.

Currently there is a log message which would allow to diagnose the issue.

%MSG-i NevisTPCGeneratorNUXMIT:  DAQ 05-Nov-2019 14:57:32 CST Booted NevisTPCNUXMIT_generator.cc:11
ConfigureStart
%MSG
terminate called after throwing an instance of 'std::future_error'
 what():  std::future_error: No associated state
DeviceFind: Failed scanning the PCI bus.
Error: 0xffffffffffffffff - Unrecognized error code

Also available in: Atom PDF