From 7dae6b162a52544b6a7cf117898584aabedc466b Mon Sep 17 00:00:00 2001 From: Jiri Podivin Date: Wed, 7 Jul 2021 07:54:34 +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: I9ee199d96044ead23db8afaa533833f68b4d81d6 --- ci/playbooks/coverchange.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ci/playbooks/coverchange.yaml b/ci/playbooks/coverchange.yaml index 61a4dff29..4194b5a10 100644 --- a/ci/playbooks/coverchange.yaml +++ b/ci/playbooks/coverchange.yaml @@ -100,7 +100,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.