-
-
Notifications
You must be signed in to change notification settings - Fork 35
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
Time based warning is not specific enough to identify source. #36
Comments
Seems good to me. |
stefanpenner
added a commit
that referenced
this issue
Dec 20, 2016
stefanpenner
added a commit
that referenced
this issue
Dec 20, 2016
I have same problems, but with |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This warning does not give enough context to know what is actually causing the output.
Seeing the following lines in my CI logs (surrounded by a thousand lines of other things) doesn't provide enough context:
I suggest that we update the warning to at least say something like:
Thoughts?
The text was updated successfully, but these errors were encountered: