-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Bug fix in DaqProvenanceHelper #28791
Conversation
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-28791/13472
|
A new Pull Request was created by @wddgit (W. David Dagenhart) for master. It involves the following packages: FWCore/Sources @makortel, @smuzaffar, @cmsbuild, @Dr15Jones can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
please test |
The tests are being triggered in jenkins. |
+1 |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
+1 |
This pull request is fully signed and it will be integrated in one of the next master IBs (tests are also fine). This pull request will now be reviewed by the release team before it's merged. @davidlange6, @silviodonato, @fabiocos (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
The tests are being triggered in jenkins. |
+1 |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
PR description:
This fixes the bug reported in issue #28786. I understand
the problem causing the exception and fixed it.
I added a call to setIsProvenanceSetOnRead on the
BranchDescription. This has been needed since
PR #28536 for FedRawDataInputSource to work
properly.
PR validation:
Using the test provided in the issue with the problem
report, I reproduced the exception and verified the
exception does not occur with the fix in place.
I somewhat narrowly focused on the reported exception.
It might be worth it for an expert responsible for
FedRawDataInputSource to verify it is really working.
Maybe the test in the bug report is sufficient, it runs
successfully to completion with the fix.