-
-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Need to understand failed tests #61
Comments
the probe does seem to detect the error, it just doesn't report it back
and its mentioned in the code |
Ok that's good. Just make sure to test it very well to work with all kinds of different errors and all commands we support. |
that's the problem. It's hard to know exactly why it fails. Best we could do is some simple regex matching |
We dont need to know why, it would probably be too difficult, as long as we detect the failure and return the output it should work fine. |
e.g. If I ping something random the hostname won't get resolved and I will get this error
But our API will keep running for 30 seconds until it times out and returns
I think it will be a major problem for our users. e.g. a user using our web tools or even CLI will get blocked for 30 seconds while he waits for a problematic test to finish.
We need a way to understand when tests fail and return the error. I dont think it should be too hard because the binary command will fail and exit, I dont understand why we have to wait for something. If the binary exited, then catch it and return the output of the error.
This applies to all commands.
The text was updated successfully, but these errors were encountered: