DPL: trigger runtime error in case of duplicate processor names#13963
DPL: trigger runtime error in case of duplicate processor names#13963ehellbar wants to merge 3 commits intoAliceO2Group:devfrom
Conversation
|
REQUEST FOR PRODUCTION RELEASES: This will add The following labels are available |
davidrohr
left a comment
There was a problem hiding this comment.
Great, thx, though didn't verify that it actually works.
|
I checked it with two workflows and one of the dummy workflows where I changed the name of one processor to match one of the other workflows. I got the error whenever I included the dummy workflow, and never without it. |
| auto found = std::find_if(physicalWorkflow.begin(), physicalWorkflow.end(), | ||
| [&name = dp.name](DataProcessorSpec const& spec) { return spec.name == name; }); | ||
| if (found == physicalWorkflow.end()) { | ||
| // also checking the workflow for processors with the same name but from a different executable, |
|
Error while checking build/O2/fullCI for 419b9db at 2025-02-17 14:54: Full log here. |
|
Error while checking build/O2/fullCI_slc9 for 419b9db at 2025-02-14 21:42: Full log here. |
419b9db to
841b74a
Compare
|
Error while checking build/O2/fullCI_slc9 for 841b74a at 2025-02-18 19:31: Full log here. |
|
Error while checking build/O2/fullCI for 841b74a at 2025-02-18 21:48: Full log here. |
…g its metadata to store executable
|
This PR did not have any update in the last 30 days. Is it still needed? Unless further action in will be closed in 5 days. |
Adding processors to the workflow if they have the same name as an already added processor but come from a different executable. This will trigger a runtime error in the
MATERIALISE_WORKFLOWstate inAliceO2/Framework/Core/src/WorkflowHelpers.cxx
Line 935 in 28d9c76