Skip to content
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

Create new main ProductRegistry if input products change #47584

Merged
merged 2 commits into from
Mar 14, 2025

Conversation

Dr15Jones
Copy link
Contributor

@Dr15Jones Dr15Jones commented Mar 12, 2025

PR description:

Instead of having one ProductRegistry shared by many objects, now if the ProductRegistry used by the Source adds new entries (which can only happen when reading a new file and the job which made the file has different dropped products) we make a new ProductRegistry and explicitly tell all Principals to update.

This would make it possible in the future to have multiple concurrent files open (open a new one while the last events in the previous file are finishing) where different Principals were using different ProductRegistries.

PR validation:

All framework unit tests pass and newly added unit test also passes.

resolves cms-sw/framework-team#1304

Only provenance of dropped ancestors are stored in ROOT files. Using untracked parameter for InputTag keeps the ProcessHistory the same so there is only one Run in the workflow.
@cmsbuild
Copy link
Contributor

cmsbuild commented Mar 12, 2025

cms-bot internal usage

@cmsbuild
Copy link
Contributor

@cmsbuild
Copy link
Contributor

A new Pull Request was created by @Dr15Jones for master.

It involves the following packages:

  • FWCore/Framework (core)
  • FWCore/Integration (core)
  • FWCore/Modules (core)
  • FWCore/TestProcessor (core)

@Dr15Jones, @cmsbuild, @makortel, @smuzaffar can you please review it and eventually sign? Thanks.
@makortel, @missirol, @wddgit this is something you requested to watch as well.
@antoniovilela, @mandrenguyen, @rappoccio, @sextonkennedy you are the release manager for this.

cms-bot commands are listed here

@Dr15Jones
Copy link
Contributor Author

please test

If the ProductRegistry of the source changes, we now create a new main ProductRegistry. The main Registry is then passed to the Principals which update their data structures.
@Dr15Jones
Copy link
Contributor Author

please test

@cmsbuild
Copy link
Contributor

@cmsbuild
Copy link
Contributor

Pull request #47584 was updated. @Dr15Jones, @makortel, @smuzaffar can you please check and sign again.

@cmsbuild
Copy link
Contributor

-1

Failed Tests: UnitTests
Size: This PR adds an extra 92KB to repository
Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-9b67e6/44947/summary.html
COMMIT: af6456c
CMSSW: CMSSW_15_1_X_2025-03-12-1100/el8_amd64_gcc12
User test area: For local testing, you can use /cvmfs/cms-ci.cern.ch/week0/cms-sw/cmssw/47584/44947/install.sh to create a dev area with all the needed externals and cmssw changes.

The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic:

You can see more details here:
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-9b67e6/44947/git-recent-commits.json
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-9b67e6/44947/git-merge-result

Unit Tests

I found 1 errors in the following unit tests:

---> test TestIOPoolInputNoParentDictionary had ERRORS

Comparison Summary

Summary:

  • You potentially added 115 lines to the logs
  • Reco comparison results: 25 differences found in the comparisons
  • DQMHistoTests: Total files compared: 50
  • DQMHistoTests: Total histograms compared: 3927028
  • DQMHistoTests: Total failures: 20
  • DQMHistoTests: Total nulls: 0
  • DQMHistoTests: Total successes: 3926988
  • DQMHistoTests: Total skipped: 20
  • DQMHistoTests: Total Missing objects: 0
  • DQMHistoSizes: Histogram memory added: 14690.869999999999 KiB( 49 files compared)
  • DQMHistoSizes: changed ( 4.22,... ): 4896.605 KiB HLT/Tracking
  • DQMHistoSizes: changed ( 7.3 ): 4897.660 KiB HLT/Tracking
  • Checked 215 log files, 184 edm output root files, 50 DQM output files
  • TriggerResults: found differences in 1 / 48 workflows

@Dr15Jones
Copy link
Contributor Author

ignore tests-rejected with manual-override

The failing unit test is expected and will clear up when run in the IB.

@makortel
Copy link
Contributor

Workflow 17034.0 shows differences in L1TEMU/L1TdeStage2uGT DQM folder. I'd guess they originate from #47423 that was tested at the same time, but the test results of that PR have already been cleaned up so I can't check. Let's run another round of tests just to make sure.

@makortel
Copy link
Contributor

@cmsbuild, please test

@cmsbuild
Copy link
Contributor

-1

Failed Tests: UnitTests
Size: This PR adds an extra 92KB to repository
Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-9b67e6/44964/summary.html
COMMIT: af6456c
CMSSW: CMSSW_15_1_X_2025-03-12-2300/el8_amd64_gcc12
User test area: For local testing, you can use /cvmfs/cms-ci.cern.ch/week0/cms-sw/cmssw/47584/44964/install.sh to create a dev area with all the needed externals and cmssw changes.

Unit Tests

I found 1 errors in the following unit tests:

---> test TestDQMGUIUpload had ERRORS

Comparison Summary

Summary:

  • No significant changes to the logs found
  • Reco comparison results: 8 differences found in the comparisons
  • DQMHistoTests: Total files compared: 50
  • DQMHistoTests: Total histograms compared: 3927484
  • DQMHistoTests: Total failures: 3
  • DQMHistoTests: Total nulls: 0
  • DQMHistoTests: Total successes: 3927461
  • DQMHistoTests: Total skipped: 20
  • DQMHistoTests: Total Missing objects: 0
  • DQMHistoSizes: Histogram memory added: 0.0 KiB( 49 files compared)
  • Checked 215 log files, 184 edm output root files, 50 DQM output files
  • TriggerResults: no differences found

@makortel
Copy link
Contributor

I don't know why the DQM GUI upload failed. It can't be from this PR (and in earlier tests that test passed)

@makortel
Copy link
Contributor

+core

@cmsbuild
Copy link
Contributor

This pull request is fully signed and it will be integrated in one of the next master IBs (test failures were overridden). This pull request will now be reviewed by the release team before it's merged. @antoniovilela, @rappoccio, @mandrenguyen, @sextonkennedy (and backports should be raised in the release meeting by the corresponding L2)

@makortel
Copy link
Contributor

ignore tests-rejected with external-failure

@mandrenguyen
Copy link
Contributor

+1

@cmsbuild cmsbuild merged commit 690f962 into cms-sw:master Mar 14, 2025
10 of 11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Create new main ProductRegistry when Source ProductRegistry changes during data processing
4 participants