You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Essentially the nested task structure before the call is
process.myTask5=cms.Task(process.d) # d is Serviceprocess.myTask8=cms.Task(process.myTask5, process.mproducer8)
process.myTask7=cms.Task(process.myTask8)
process.myTask6=cms.Task(process.myTask7)
process.myTask1=cms.Task(process.myTask6, ...)
operates first on process.myTask8 and sets its value to be cms.Task(process.mproducer8). Then the loop operates on process.myTask1, and nothing needs to be done.
In py3 build the loop operates first on process.myTask1. The visitor proceeds up to myTask8, removes the myTask5, and, because values were changed, recreates the nested task structure with anonymous Tasks
The anonymous Tasks lead to the failure of the test that expects to see process.myTask6 in the dumpPython() output. As far as I can tell, the issue affects only the dumpPython(), the module/component contents of the tasks are still correct.
The text was updated successfully, but these errors were encountered:
The python 3 unit test failure
seems to be caused by a different order of Tasks whose
replace()
functions are called by this linecmssw/FWCore/ParameterSet/python/Config.py
Line 2387 in a04e878
Essentially the nested task structure before the call is
In the py2 build, this loop
cmssw/FWCore/ParameterSet/python/Config.py
Lines 1071 to 1074 in a04e878
operates first on
process.myTask8
and sets its value to becms.Task(process.mproducer8)
. Then the loop operates onprocess.myTask1
, and nothing needs to be done.In py3 build the loop operates first on
process.myTask1
. The visitor proceeds up tomyTask8
, removes themyTask5
, and, because values were changed, recreates the nested task structure with anonymous Taskscmssw/FWCore/ParameterSet/python/SequenceTypes.py
Lines 1275 to 1280 in a04e878
i.e. to
The anonymous Tasks lead to the failure of the test that expects to see
process.myTask6
in thedumpPython()
output. As far as I can tell, the issue affects only thedumpPython()
, the module/component contents of the tasks are still correct.The text was updated successfully, but these errors were encountered: