On Sun, Mar 4, 2018 at 11:48 PM, Daniel Ruggeri <[email protected]> wrote: > > I'd like to ask a followup question... how do we catch this in the > test suite? With this (100% failure), ab still returns a 0 exit code. > It *does* at least give the error message to STDERR. Perhaps we > should add to the test suite that `ab -q` completed against the http > and https vshosts with no lines printed to STDERR and has a 0 exit > code?
The best way is probably to capture stderr... In this case though, this is not exactly "100% failure" in any circonstances, for instance on localhost (or fast enough local network) it won't fail since the errorneous path is not taken when non-blocking connect succeeds. It might not be easy/wise to launch/automate "ab" on an external server in a test suite... Regards, Yann.
