Browse Source

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 <jpodivin@redhat.com>
Change-Id: Ia7b9951d5c47c13f344fc1303604018f2420c457
changes/37/799737/1
Jiri Podivin 2 months ago
parent
commit
8a87da12bf
  1. 2
      playbooks/coverchange.yaml

2
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.
Loading…
Cancel
Save