-
Notifications
You must be signed in to change notification settings - Fork 327
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
Improve GL error report messages #883
Comments
My vote is that it is more important to get all the GL errors in pace first, rather make the code more complex by adding the custom error messages for a few. So I would just drop the text if it does not make sense, or just drop all the texts for now. Let's do the simple thing first, and do the complex solution later please? |
We could provide the URL for the online help for the given command - that should make it possible for the user to lookup what caused the error. It is not ideal, but it is simple to start with. |
Also note that drivers can provide string messages together with the errors. Maybe we should use those for now? |
I'm fine with removing the variable names from the message as a first step - that would lower the priority to p3. |
That should probably work - I will take a look. |
Thanks! |
The new debug.py script is meant to be used as a basis when running one-off swarming tasks to diagnose failures. Bug: n/a Test: manual runs of debub.py on Swarming bots
We still have nonsense being displayed for GL errors. We need to fix this.
Example:
Invalid value "value" for "variable"
The text was updated successfully, but these errors were encountered: