-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Using LarG4Detector v6 in fdhd 1x2x2 #132
base: develop
Are you sure you want to change the base?
Conversation
trigger build |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Small .fcl changes that shouldn't break the build. I will test the reconstruction with CI before releasing.
✔️ 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 DUNE Failed at phase ci_tests DUNE on slf7 for c14:prof - ignored failure for unit_test -- details available through the CI dashboard 🚨 For more details about the failed phase, check the ci_tests DUNE phase logs parent CI build details are available through the CI dashboard |
Something is not quite right with the way these .fcl files affect other detector services. You can see an example failed test at https://dbweb8.fnal.gov:8443/LarCI/app/ns:dune/storage/docs/2025/01/31/test_DetectorProperties.log The full list of failed tests is at https://dbweb8.fnal.gov:8443/LarCI/app/ns:dune/build_detail/phase_details?build_id=dune_ci/18696&platform=Linux%20slf7&phase=unit_test&buildtype=slf7%20c14:prof |
❌ CI build for DUNE Failed at phase ci_tests DUNE on slf7 for e26:prof - ignored failure for unit_test -- details available through the CI dashboard 🚨 For more details about the failed phase, check the ci_tests DUNE phase logs parent CI build details are available through the CI dashboard |
The fact that that table can't be found might be related to the fact that the dunesim version which dunecore is building against does not include dunesim MR # 83. A build against tagged version v10_03_01d02 should work. Do you agree? |
Depends on DUNE/dunesim#83 being approved. Using the new geometry v6 table instead of the v4 one.