[checkmk-commits] [tribe29/checkmk] 55e226: cpu_tracking: Fully localize CPUTracker usage

Branch: refs/heads/master Home: https://github.com/tribe29/checkmk Commit: 55e226ced3270ca01db5c7cbfd24510d89f5aa27 https://github.com/tribe29/checkmk/commit/55e226ced3270ca01db5c7cbfd24510d8… Author: Mathias Laurin <mathias.laurin(a)tribe29.com> Date: 2020-10-27 (Tue, 27 Oct 2020) Changed paths: M cmk/base/checkers/_abstract.py M cmk/base/checkers/agent.py M cmk/base/checkers/ipmi.py M cmk/base/checkers/piggyback.py M cmk/base/checkers/programs.py M cmk/base/checkers/snmp.py M cmk/base/checkers/tcp.py M cmk/base/checking.py M cmk/fetchers/controller.py M cmk/utils/cpu_tracking.py M tests/unit/cmk/base/checkers/test_agent.py M tests/unit/cmk/base/checkers/test_ipmi_management_board_data_source.py M tests/unit/cmk/base/checkers/test_program_data_source.py M tests/unit/cmk/base/checkers/test_snmp_data_source.py M tests/unit/cmk/fetchers/test_controller.py M tests/unit/cmk/utils/test_cpu_tracking.py Log Message: ----------- cpu_tracking: Fully localize CPUTracker usage Now that we do not have globals for cpu tracking anymore, we can fully localize user code by letting CPUTracker objects track a single phase. * CPUTracker does not need to keep track of the phases anymore. This simplifies its module and clarifies its usage. * Now, users *must* handle the CPU data explicitly--or it is gone. * The Sources do not need to track the fancy CPU tracker phase name that they were not using anyway. CMK-5920 Change-Id: Ibfc750ec4dc286aaf207beb5c1dd0cab03eaff66