Project

General

Profile

Bug #18305

TimeTracker database output option sometimes causes exception

Added by David Brown over 1 year ago. Updated over 1 year ago.

Status:
Remission
Priority:
Normal
Assignee:
-
Category:
Metadata
Target version:
-
Start date:
11/16/2017
Due date:
% Done:

0%

Estimated time:
Occurs In:
Scope:
Internal
Experiment:
Mu2e
SSI Package:
art
Duration:

Description

I am using the dbOutput (SQLite) output of TimeTracker to study module timing distributions. This works when I create a new file for each run. If instead I use the 'overwrite' option (overwrite : true) to overwrite an existing file, art sometimes issues an exception, noted below. The exception seems to be issued randomly (rerunning the same job multiple times produces different results), but is fairly consistently produced when processing more events the 2nd time than the first.

%MSG-s ArtException: Early 30-Oct-2017 16:04:12 CDT JobSetup
cet::exception caught in art
---- OtherArt BEGIN
  ServiceCreation
  ---- SQLExecutionError BEGIN
    database disk image is malformed
  ---- SQLExecutionError END
  cet::exception caught during construction of service type
art::TimeTracker:
---- OtherArt END
%MSG
Art has completed and will exit with status 1

As a more minor but annoying issue, I note that, without the overwrite option, if I try to write to the same database file, the exception message is obscure and doesn't help the user understand what the problem is.

Transaction d'tor called before commit was called.
terminate called after throwing an instance of
'cet::coded_exception<cet::sqlite::errors::ErrorCodes,
&cet::sqlite::ExceptionDetail::translate[abi:cxx11]>'
  what():  ---- SQLExecutionError BEGIN
  Failed to bind int64.
  Return code: 21
---- SQLExecutionError END

History

#1 Updated by Christopher Green over 1 year ago

  • Category set to Metadata
  • Status changed from New to Assigned
  • Assignee set to Kyle Knoepfel

We will attempt to reproduce and resolve the primary issue, and produce a more informative message in the second case.

#2 Updated by Kyle Knoepfel over 1 year ago

Dave, can you provide a sample job that demonstrates this (sporadic) failure? I need to know:

  • the machine you're running on (e.g. mu2egpvm01)
  • the version of mu2e Offline you're using if the job depends on anything from there
  • ideally, the version of art--the "Occurs In" field says you observe this is 1.03.09, which does not correspond to a version of art.

#3 Updated by Kyle Knoepfel over 1 year ago

  • Description updated (diff)

#4 Updated by Kyle Knoepfel over 1 year ago

  • Status changed from Assigned to Feedback

#5 Updated by David Brown over 1 year ago

I have not been able to reproduce this error. I suggest we close this issue for now.

#6 Updated by Kyle Knoepfel over 1 year ago

  • Status changed from Feedback to Remission
  • Assignee deleted (Kyle Knoepfel)

Thank you, Dave, for the extra information. I will put the issue in "Remission" state to reflect that it may still be an issue later on.

#7 Updated by Kyle Knoepfel over 1 year ago

  • Occurs In 2.07.03 added
  • Occurs In deleted (1.03.09)
  • SSI Package art added


Also available in: Atom PDF