Skip to content

Update CI FHiCLs in production branch#873

Merged
jas1005 merged 12 commits intorelease/SBN2025Afrom
feature/vito_update_ci_prod
Apr 22, 2026
Merged

Update CI FHiCLs in production branch#873
jas1005 merged 12 commits intorelease/SBN2025Afrom
feature/vito_update_ci_prod

Conversation

@vitodb
Copy link
Copy Markdown
Contributor

@vitodb vitodb commented Dec 2, 2025

This PR is to update the set of FHiCL files used by the CI for the three MC workflow we currently test with the CI, these are:

  • single
  • nucosmics
  • intimecosmic
    This also update some standard FHiCL to update them with current code.

With this PR we should be able to run regression test for the production branch.

@vitodb vitodb requested review from SFBayLaser and cerati December 2, 2025 20:01
@vitodb vitodb changed the title Update CI FHiCLs Update CI FHiCLs in production branch Dec 2, 2025
@vitodb vitodb requested a review from gputnam December 2, 2025 20:59
@FNALbuild
Copy link
Copy Markdown
Collaborator

✔️ CI build for LArSoft Succeeded on slf7 for c14:prof -- details available through the CI dashboard

@FNALbuild
Copy link
Copy Markdown
Collaborator

✔️ CI build for LArSoft Succeeded on slf7 for e26:prof -- details available through the CI dashboard

@FNALbuild
Copy link
Copy Markdown
Collaborator

❌ 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

@FNALbuild
Copy link
Copy Markdown
Collaborator

⚠️ CI build for ICARUS Warning at phase ci_tests ICARUS on slf7 for e26:prof - ignored warnings for build -- details available through the CI dashboard

🚨 For more details about the warning phase, check the ci_tests ICARUS phase logs

parent CI build details are available through the CI dashboard

@jas1005
Copy link
Copy Markdown
Contributor

jas1005 commented Apr 3, 2026

@vitodb

Is this PR still needed given PR #874 made it into develop? I'm almost certain I can close this, but I wanted to check with you first.

@vitodb
Copy link
Copy Markdown
Contributor Author

vitodb commented Apr 3, 2026

I think this PR can be closed. This was specifically for release/SBN2025A branch, so if this branch is not used anymore we can close this PR.
As you mentioned, the corresponding PR #874 for develop branch was already merged, so there is no need to migrate this PR to develop branch.

@jas1005
Copy link
Copy Markdown
Contributor

jas1005 commented Apr 3, 2026

Given Vito's above comments, I am closing this PR. The changes have already been applied to develop in another PR.

@jas1005 jas1005 closed this Apr 3, 2026
@jas1005 jas1005 deleted the feature/vito_update_ci_prod branch April 3, 2026 18:08
@jas1005 jas1005 restored the feature/vito_update_ci_prod branch April 20, 2026 13:22
@jas1005
Copy link
Copy Markdown
Contributor

jas1005 commented Apr 20, 2026

There will be further development on release/SBN2025A for the Production team. Reopening this PR, which mirrors developments already merged into develop.

@jas1005 jas1005 reopened this Apr 20, 2026
@FNALbuild
Copy link
Copy Markdown
Collaborator

✔️ CI build for LArSoft Succeeded on slf7 for c14:prof -- details available through the CI dashboard

@FNALbuild
Copy link
Copy Markdown
Collaborator

❌ 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

@FNALbuild
Copy link
Copy Markdown
Collaborator

✔️ CI build for LArSoft Succeeded on slf7 for e26:prof -- details available through the CI dashboard

@FNALbuild
Copy link
Copy Markdown
Collaborator

❌ 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

@SBNSoftware SBNSoftware deleted a comment from leoaliaga Apr 20, 2026
@jas1005
Copy link
Copy Markdown
Contributor

jas1005 commented Apr 20, 2026

trigger build larsoft@v10_06_00_02 LArSoft/lar*@LARSOFT_SUITE_v10_06_00_02 SBNSoftware/sbnalg@v10_06_00_05 SBNSoftware/sbnobj@v10_01_01_01 SBNSoftware/sbnanaobj@v10_00_05_02 SBNSoftware/sbndaq-artdaq-core@v1_10_06 SBNSoftware/sbncode@v10_06_00_06 SBNSoftware/icarusutil@v10_06_00_04

@FNALbuild
Copy link
Copy Markdown
Collaborator

✔️ CI build for LArSoft Succeeded on slf7 for c14:prof -- details available through the CI dashboard

@FNALbuild
Copy link
Copy Markdown
Collaborator

✔️ CI build for LArSoft Succeeded on slf7 for e26:prof -- details available through the CI dashboard

@FNALbuild
Copy link
Copy Markdown
Collaborator

❌ 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

@FNALbuild
Copy link
Copy Markdown
Collaborator

❌ CI build for ICARUS Failed at phase ci_tests ICARUS on slf7 for e26:prof - ignored warnings for build -- details available through the CI dashboard

🚨 For more details about the failed phase, check the ci_tests ICARUS phase logs

parent CI build details are available through the CI dashboard

@jas1005
Copy link
Copy Markdown
Contributor

jas1005 commented Apr 22, 2026

Merging this PR into release/SBN2025A despite some CI tests failing. These failures are known and are currently being diagnosed. This is being done to merge in PR #897 and expressly start production activities. While this PR does not fix all of our CI issues, it is undoubtedly a step in the right direction.

@jas1005 jas1005 merged commit e5bc7b1 into release/SBN2025A Apr 22, 2026
2 of 4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants