Project

General

Profile

Bug #13564

Assertion failure on maybeInvalidateRangeSet(): Assertion `!principalRS.ranges().empty()' failed.

Added by Lucas Mendes santos about 3 years ago. Updated about 3 years ago.

Status:
Closed
Priority:
Immediate
Assignee:
Category:
Infrastructure
Target version:
Start date:
08/16/2016
Due date:
% Done:

100%

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

Description

Hi guys,

Found an issue on art v2.2. When I run a reconstruction fhicl file it runs accordingly until it creates the art-root output. There I get this error:

lar: /scratch/workspace/nu-release-build/v2_03_00/s39-e10/debug/build/art/v2_02_02/src/art/Framework/IO/Root/RootOutputFile.cc:230: void {anonymous}::maybeInvalidateRangeSet(art::BranchType, const art::RangeSet&, art::RangeSet&): Assertion `!principalRS.ranges().empty()' failed.

Did a scan with Gianluca Petrillo and even though we run a empty fhicl file the error persists. Currently, I'm running on the latest version of lariatsoft (v06_03_00)

The path to the input file list is /pnfs/lariat/scratch/users/lmendes/v06_03_00/digits2/files.list

Thanks in advance,

Lucas


Related issues

Related to art - Bug #14430: Art v2_05_00 failed assertion.Closed11/07/2016

History

#1 Updated by Kyle Knoepfel about 3 years ago

  • Subject changed from Crash on maybeInvalidateRangeSet(): Assertion `!principalRS.ranges().empty()' failed. to Assertion failure on maybeInvalidateRangeSet(): Assertion `!principalRS.ranges().empty()' failed.
  • Status changed from New to Assigned
  • Assignee set to Kyle Knoepfel

Do you get an error if you run with the profile build of lariatsoft?

#2 Updated by Kyle Knoepfel about 3 years ago

I confirm the abort using the first file in the file list you pointed me to, and also the version of lariatsoft you are using. Investigating.

#3 Updated by Lucas Mendes santos about 3 years ago

Kyle Knoepfel wrote:

I confirm the abort using the first file in the file list you pointed me to, and also the version of lariatsoft you are using. Investigating.

In the profile build I don't get the error. Interesting.

#4 Updated by Kyle Knoepfel about 3 years ago

This is not surprising. assert is a preprocessor macro that is disabled for the profile build--in other words, the code encapsulated by an assert statement does not even appear in the compiled product.

The bug you encountered is understood. When implementing the range-set capabilities of art 2.01.00, the backwards-compatibility I had accounted for was obviously inadequate. Various options are possible in fixing this bug, but we would like to discuss them with the art stakeholders this Thursday.

#5 Updated by Kyle Knoepfel about 3 years ago

  • Category set to Infrastructure
  • Status changed from Assigned to Resolved
  • % Done changed from 0 to 100
  • SSI Package art added
  • SSI Package deleted ()

#6 Updated by Kyle Knoepfel about 3 years ago

Fixed with commit art:936e5932. With the fix, I confirm that running the debug build of lariatsoft v06_03_00, with the configuration you provided, is successful.

#7 Updated by Kyle Knoepfel about 3 years ago

  • Status changed from Resolved to Closed
  • Target version set to 2.03.00

#8 Updated by Kyle Knoepfel almost 3 years ago

  • Related to Bug #14430: Art v2_05_00 failed assertion. added


Also available in: Atom PDF