Reenable CVN - #636
Conversation
…ature/tjyang_cvnfix" This reverts commit 4b98180.
|
This PR can only be merged after we move to larsoft v10_04_01. |
absolution1
left a comment
There was a problem hiding this comment.
Thanks @yangtj207
These changes look nice, simple, and mostly functionising some calls
|
trigger build LArSoft/lar*@LARSOFT_SUITE_v10_04_01 SBNSoftware/sbndaq-artdaq-core@v1_10_04 SBNSoftware/sbncode@v10_04_01 |
|
✔️ CI build for LArSoft Succeeded on slf7 for c14:prof -- details available through the CI dashboard |
|
✔️ CI build for LArSoft Succeeded on slf7 for e26:prof -- details available through the CI dashboard |
|
❌ CI build for SBND Failed at phase build SBND on slf7 for c14:prof -- details available through the CI dashboard 🚨 For more details about the failed phase, check the build SBND phase logs parent CI build details are available through the CI dashboard |
|
✔️ CI build for SBND Succeeded on slf7 for e26:prof -- details available through the CI dashboard parent CI build details are available through the CI dashboard |
|
Approved |
Description
Reenable CVN after changes in larsoft v10_04_01.
Checklist
Reviewers,AssigneesDevelopementRelevant PR links (optional)
Does this PR require merging another PR in a different repository (such as sbnanobj/sbnobj etc.)?
We need larsoft version >= v10_04_01.
Link(s) to docdb describing changes (optional)
Is there a docdb describing the issue this solves or the feature added?