From 653f190ed7748f3b2fadbb5c5c8460c986b65769 Mon Sep 17 00:00:00 2001 From: pavel-zotov Date: Sat, 13 May 2023 20:32:27 +0300 Subject: [PATCH] Added/Updated tests\bugs\core_6348_test.py: added 'perf_issue_tag' string to the output related to performance problem. This text will serve as 'tag' for unambiguous detection of performance problem and set appropriate mark to the test outcome. --- tests/bugs/core_6348_test.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tests/bugs/core_6348_test.py b/tests/bugs/core_6348_test.py index 212d966a..eccb6a48 100644 --- a/tests/bugs/core_6348_test.py +++ b/tests/bugs/core_6348_test.py @@ -164,7 +164,7 @@ def test_1(act: Action, tmp_data: Path, capsys): if locals()[var_name] <= MAX_THRESHOLD_FOR_COMPRESS_ON_VS_OFF: print(msg_prefix + 'OK, acceptable.') else: - print(msg_prefix + 'TOO HIGH: %9.2f - more than threshold: %6.2f' % ( locals()[var_name], MAX_THRESHOLD_FOR_COMPRESS_ON_VS_OFF ) ) + print(msg_prefix + '/* perf_issue_tag */ TOO HIGH: %9.2f - more than threshold: %6.2f' % ( locals()[var_name], MAX_THRESHOLD_FOR_COMPRESS_ON_VS_OFF ) ) act.stdout = capsys.readouterr().out assert act.clean_stdout == act.clean_expected_stdout