From 785aec274f9d086d3562647a085783ccd65be7a7 Mon Sep 17 00:00:00 2001 From: Andrew Grimberg Date: Wed, 5 Oct 2022 08:57:49 -0700 Subject: [PATCH] CI: Disable second bashate call CI is having an issue with the second call to bashate which is supposed to warn on lines > 80 characters. I cannot seem to get this to replicate properly locally and bashate is still not a hard requirement for our CI, we're disabling the extra call for now. Issue: RELENG-4467 Change-Id: I2bf092b8026d60848796f3357e46d3e877417896 Signed-off-by: Andrew Grimberg --- tox.ini | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tox.ini b/tox.ini index 9f939e30..e5ae4d93 100644 --- a/tox.ini +++ b/tox.ini @@ -90,7 +90,7 @@ commands = # forbid lines > 120 char sh -c "find . -not -path '*/\.*' -name '*.sh' -exec bashate -e E006 -i $RULES_IGNORED --max-line-length 120 \{\} +" # perform bashate and warn lines > 80 char - find . -not -path '*/\.*' -name *.sh -exec bashate \{\} + + #find . -not -path '*/\.*' -name *.sh -exec bashate \{\} + #The option --max-line-length 80 is used by default. ######### -- 2.16.6