From 255ed06075654850d033178dfa038a1bf4b48f6c Mon Sep 17 00:00:00 2001
From: Ian Wienand <iwienand@redhat.com>
Date: Wed, 27 Jul 2022 17:16:19 +1000
Subject: [PATCH] ansible-lint: disable progressive mode

Progressive mode

 ... makes the linter return a success even if some failures are
 found, as long the total number of violations did not increase since
 the previous commit.

I have found what I think is inconsistent matching of the errors
between runs and I'm not sure it isn't hiding problems.  We are
linter-clean and gate on the linter passing, so we don't need to do
this two-pass system.

Change-Id: I47be01a095d80dfb4d15f90da7bce49c3d42a2dd
---
 tox.ini | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/tox.ini b/tox.ini
index 8d355e8ca..8907118bc 100644
--- a/tox.ini
+++ b/tox.ini
@@ -49,7 +49,7 @@ commands =
   flake8 {posargs}
   yamllint -s -f parsable .
   python -m ansiblelint --version
-  python -m ansiblelint {env:ANSIBLELINT_OPTS:--progressive}
+  python -m ansiblelint {env:ANSIBLELINT_OPTS:}
   # Ansible Syntax Check
   {toxinidir}/tools/check_jobs_documented.py
   {toxinidir}/tools/update-test-platforms.py