From 205f96af65ab880c572711a0a2a982f904532a55 Mon Sep 17 00:00:00 2001 From: Jiri Podivin Date: Wed, 7 Jul 2021 07:53:43 +0200 Subject: [PATCH] fix var name in logging statement The variable referenced in the logging statement of the job was not the one on which the assertion was made. As a result the message was confusing. Signed-off-by: Jiri Podivin Change-Id: I56bfd351ab3be0d9f3c87694692f878d00d45c4f --- playbooks/coverchange.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/playbooks/coverchange.yaml b/playbooks/coverchange.yaml index 78ddc35..04d31b5 100644 --- a/playbooks/coverchange.yaml +++ b/playbooks/coverchange.yaml @@ -94,7 +94,7 @@ assert: that: "{{ (coverage_after_total.stdout | float) }} >= {{ (coverage_before_total.stdout | float) }}" fail_msg: | - Before the change {{ (coverage_before.stdout | float)*100 }}% of the lines were covered. + Before the change {{ (coverage_before_total.stdout | float)*100 }}% of the lines were covered. Now it's {{ (coverage_after_total.stdout | float )*100 }}%. Did you write your unit tests? success_msg: | Code coverage check successful, {{ (coverage_before_total.stdout | float) * 100 }}% of code is now covered.