Project

General

Profile

Bug #22194

DAQInterface v3_04_00 has problems saving the run record to the database

Added by John Freeman 6 months ago. Updated 6 months ago.

Status:
Reviewed
Priority:
Normal
Assignee:
Category:
-
Target version:
-
Start date:
03/22/2019
Due date:
% Done:

100%

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

Description

This was discovered this afternoon as part of SBND testing. Basically, there are two problems:

-put_config_info_base performs a "sanity check" which doesn't account for the fact that "localhost" and "$HOSTNAME" are referring to the same node
-In the call to archiveRunConfiguration, the now-nonexistent self.config_for_run variable is passed; it's nonexistent because DAQInterface now thinks of the config as a set of subconfigs

Associated revisions

Revision 0537d22d (diff)
Added by John Freeman 6 months ago

JCF: perform bugfixes described in Issue #22194 to fix the saving of the run record to the database

History

#1 Updated by John Freeman 6 months ago

  • % Done changed from 0 to 100
  • Assignee set to John Freeman
  • Status changed from New to Resolved

Changes are available on commit 0537d22dc9062a3843872c7b98ab17cc31da8a92 of feature/issue22194_save_to_database.

#2 Updated by Gennadiy Lukhanin 6 months ago

  • Status changed from Resolved to Reviewed


Also available in: Atom PDF