Skip to content
Snippets Groups Projects
Forked from atlas / athena
88968 commits behind the upstream repository.
  • Frank Winklmeier's avatar
    15ab2d7d
    TriggerMenuMT: Stop producing L1 menu files during build · 15ab2d7d
    Frank Winklmeier authored
    The main change is to no longer produce the L1 menu files (.xml, .json)
    during the build and not install them any longer as part of the release.
    This technique was inherited from `TriggerMenuXML`, but no current job
    actually uses these pre-generated files. This simplifies the cmake
    configuration greatly and `TriggerMenuMT` is no longer forced to run at
    the end of the build.
    
    To ensure menus are working, add a unit test for each L1 menu.
    
    Some unrelated package cleanup:
    - Delete unused `testMenuMT.sh`, `trigermenuMT_test.py`, `generateMenuMT.py`.
    - Delete `generateMT.py` and instead inline the flags in `test_HLTmenu.sh`.
    - Move `menu_config_tests.py` to `python/` directory.
    15ab2d7d
    History
    TriggerMenuMT: Stop producing L1 menu files during build
    Frank Winklmeier authored
    The main change is to no longer produce the L1 menu files (.xml, .json)
    during the build and not install them any longer as part of the release.
    This technique was inherited from `TriggerMenuXML`, but no current job
    actually uses these pre-generated files. This simplifies the cmake
    configuration greatly and `TriggerMenuMT` is no longer forced to run at
    the end of the build.
    
    To ensure menus are working, add a unit test for each L1 menu.
    
    Some unrelated package cleanup:
    - Delete unused `testMenuMT.sh`, `trigermenuMT_test.py`, `generateMenuMT.py`.
    - Delete `generateMT.py` and instead inline the flags in `test_HLTmenu.sh`.
    - Move `menu_config_tests.py` to `python/` directory.
Code owners
Assign users and groups as approvers for specific file changes. Learn more.
CMakeLists.txt 2.19 KiB