Post event transition cache must be atomic #21320
Conversation
The transition which occurs right after the last event in a block is cached in order to be transferred to the main thread. This cached value needs to be atomic to force synchronization of the memory.
|
The code-checks are being triggered in jenkins. |
|
+code-checks |
|
A new Pull Request was created by @Dr15Jones (Chris Jones) for master. It involves the following packages: FWCore/Framework @cmsbuild, @smuzaffar, @Dr15Jones can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
|
Please test |
|
+1 |
cmsbuild
added
core-approved
fully-signed
and removed
core-pending
pending-signatures
labels
|
The tests are being triggered in jenkins. |
|
This pull request is fully signed and it will be integrated in one of the next master IBs after it passes the integration tests. This pull request will now be reviewed by the release team before it's merged. @davidlange6, @slava77, @smuzaffar (and backports should be raised in the release meeting by the corresponding L2) |
|
+1 The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic: |
|
Comparison job queued. |
|
+1 |
|
Comparison is ready Comparison Summary:
|
The transition which occurs right after the last event in a block is cached in order to be transferred to the main thread. This cached value needs to be atomic to force synchronization of the memory.