Release 0.7.6 breaks --fail-any-none flag

[amoskyler]

Since the release of 0.7.6 earlier this month --fail-any-none is exiting the application with status code 255 instead of 0. When I downgrade the package to 0.7.5 it works as expected.

All tasks in my state are completing successfully, so as you can imagine I am a bit confused. I have also had trouble finding what code changed in that release, so I'm having trouble tracking down why it is not behaving the way I expect.

[mattiasr]

I think this is related, it also worked in 0.7.5 but got broken in 0.7.6

$ pepper --fail-any -C 'G@roles:postgresql-server and G@env:foo-stage' state.apply foo.db.bar.create SALTENV=0.0.22
{
    "return": [
        {
            "cool.host.name": {
                "jid": "20200824064732796944",
                "out": "highstate",
                "ret": [
                    "No matching sls found for 'foo.db.bar.create' in env '0.0.22'"
                ],
                "retcode": 1
            }
        }
    ]
}


$ echo $?
0

With 0.7.5 it exit with 1