emergency fix for the errors introduced by DirectInputModule
Well, I guess that the lesson here should be always to write unit tests when if statements are involved, not just rely on the integration tests. On th plus side the new infrastructure made it a lot easier to test this, and I may have fixed a longer-standing bug since the previous implementation had never been tested.
Showing
- PhysicsAnalysis/D3PDTools/EventLoop/CMakeLists.txt 7 additions, 1 deletionPhysicsAnalysis/D3PDTools/EventLoop/CMakeLists.txt
- PhysicsAnalysis/D3PDTools/EventLoop/EventLoop/ModuleData.h 5 additions, 0 deletionsPhysicsAnalysis/D3PDTools/EventLoop/EventLoop/ModuleData.h
- PhysicsAnalysis/D3PDTools/EventLoop/Root/DirectInputModule.cxx 15 additions, 10 deletions...csAnalysis/D3PDTools/EventLoop/Root/DirectInputModule.cxx
- PhysicsAnalysis/D3PDTools/EventLoop/Root/ModuleData.cxx 7 additions, 0 deletionsPhysicsAnalysis/D3PDTools/EventLoop/Root/ModuleData.cxx
- PhysicsAnalysis/D3PDTools/EventLoop/Root/Worker.cxx 1 addition, 0 deletionsPhysicsAnalysis/D3PDTools/EventLoop/Root/Worker.cxx
- PhysicsAnalysis/D3PDTools/EventLoop/test/gt_DirectInputModule.cxx 201 additions, 0 deletions...nalysis/D3PDTools/EventLoop/test/gt_DirectInputModule.cxx
Loading
-
mentioned in merge request !65948 (merged)
-
mentioned in commit 32f74eb0
Please register or sign in to comment