Imported AssnsCrosser algorithm from icarusalg [3/3]#825
Conversation
|
trigger build larsoft@v10_06_00 LArSoft/lar*@LARSOFT_SUITE_v10_06_00 SBNSoftware/sbnalg@v10_06_00_01 SBNSoftware/sbncode@v10_06_00_01 SBNSoftware/sbnalg#2 |
|
✔️ CI build for LArSoft Succeeded on slf7 for e26:prof -- details available through the CI dashboard |
|
✔️ CI build for LArSoft Succeeded on slf7 for c14:prof -- details available through the CI dashboard |
|
❌ CI build for ICARUS Failed at phase build ICARUS on slf7 for e26:prof -- details available through the CI dashboard 🚨 For more details about the failed phase, check the build ICARUS phase logs parent CI build details are available through the CI dashboard |
|
❌ CI build for ICARUS Failed at phase build ICARUS on slf7 for c14:prof -- details available through the CI dashboard 🚨 For more details about the failed phase, check the build ICARUS phase logs parent CI build details are available through the CI dashboard |
SFBayLaser
left a comment
There was a problem hiding this comment.
Obviously this has to wait until included in sbnalg but I agree this is a good addition and change.
|
@PetrilloAtWork, I'm unable to get ICARUSAlg PR 94 to build with the latest build command in that PR. The culprit seems to be in this sibling PR for ICARUSCode. From the following segment of the logs for build 14579, I think that the issue is something in the
|
This is a dependent PR of SBNSoftware/sbnalg#2: see that PR for details.
This PR updates header paths and namespaces after the move of code from
icarusalgtosbnalg.Only @SFBayLaser to review this one.