Warnings cause exit code 1 by default
See original GitHub issuePassing -1 to the --max-warnings flag is no longer supported. Simply omit the flag for the same behavior.
Ref: https://github.com/lesshint/lesshint/releases/tag/v3.0.0
Which version of lesshint
are you using?
3.3.1.
Executing: lesshint ./src
(without -x
flag), exits with code 1 and breaks my build.
What did you expect to happen? Exit with code 0.
What’s the actual result? Exit with code 1.
I did try with -x false
etc., but it’s always the same effect. It only works when I use a number, but I don’t want to do that. For sure it doesn’t work as states in the docs.
Issue Analytics
- State:
- Created 6 years ago
- Comments:8 (6 by maintainers)
Top Results From Across the Web
How to Fix 'Terminated With Exit Code 1' Error - Komodor
Exit Code 1 indicates that a container shut down, either because of an application failure or because the image pointed to an invalid...
Read more >Troubleshooting 'terminated with exit code 1' error - ContainIQ
Kubernetes pod terminations that report exit code 1 indicate something has gone wrong inside the pod's container. The application will have crashed, causing...
Read more >[rush] allowWarningsInSuccessfulBuild is not works #2703
So that process returns exit code 1 , which rolls up to rush bootstrap:buildsdk and fails the outer command. 1
Read more >error Command failed with exit code 1. when I try to run yarn
I am learning reactjs - nodejs I was trying to run the server so I installed yarn, nodemon, express but when I try...
Read more >warnings — Warning control — Python 3.11.1 documentation
"default". print the first occurrence of matching warnings for each location (module + line number) where the warning is issued. "error".
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hmm, something isn’t correct, yes. I’m not sure if it’s a docs issue, a bug, or something else just yet (I’ve been thinking of changing the exit code behaviour when there’s only warnings too).
Let me think about it for a little while.
@jwilsson sure, I can do that.