Fix case where external work was only module running on a stream #23757
Conversation
There was a bug where if there was an external work and we only ever had one module running at a time on a stream, the external work was not added to the stacked graph at the bottom.
|
The code-checks are being triggered in jenkins. |
|
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-23757/5430 |
|
please test |
|
+1 |
cmsbuild
added
code-checks-approved
core-approved
fully-signed
and removed
code-checks-pending
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, @fabiocos (and backports should be raised in the release meeting by the corresponding L2) |
|
A new Pull Request was created by @Dr15Jones (Chris Jones) for master. It involves the following packages: FWCore/Concurrency @cmsbuild can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
|
+1 The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic: |
|
Comparison job queued. |
|
Comparison is ready Comparison Summary:
|
|
+1 |
There was a bug where if there was an external work and we only ever had one module running at a time on a stream, the external work was not added to the stacked graph at the bottom.