Closed plexoos closed 3 months ago
This is not reproducible in the production environment (i.e. built on an rcas node). Could you point me to instructions on how to load the container that the test runs in?
@plexoos
This issue can be resolved by circumventing the use of inlined non-const map accessors. E.g. https://github.com/star-bnl/star-sw/pull/619/commits/a9609e73adf77644ee60b61972ee61c064e0a954
Could you point me to instructions on how to load the container that the test runs in?
Very easy. Download an artifact from the Build Pull Request action page, create a docker image with docker load < star-sw-root6-gcc485.tar
, then run it
Okay. Have things running under docker. Unfortunately no GDB. However, once I built the star-sw under the eval area in afs, I was able to reproduce the issue in the production environment.
The problem occurs when the StiMasterDetectorBuilder tries to create a copy (clone) of the geometry. The crash appears to happen inside of root. I can reproduce this very simply by doing
# Load a geometry macro
$ root.exe y2012.C
# Clone the geometry
gGeoManager->Clone("CloneGeom");
*** Break *** segmentation violation
Generating stack trace...
So... moving to 6.24 will require a workaround (or bug fix in root). In the past we have not cloned the geometry, but rather operated on the geometry in memory and then restored from a cached file. So we should have a workaround available. Will return to this tomorrow.
After a couple of fixes, our code seems to compile fine against ROOT6.24 (See https://github.com/star-bnl/star-sw/pull/619)
However, some test jobs fail at what appears to be the geometry loading stage. The errors point to the code in
StarVMC/StarAgmlLib
. Here is an example error message:https://github.com/star-bnl/star-sw/actions/runs/6727541469/job/18287828236?pr=619
cc @klendathu2k @fgeurts