-
Notifications
You must be signed in to change notification settings - Fork 119
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
Build Cop: group issues for related tests when it makes sense #258
Comments
cc @fhinkel |
I queried to get all issues for test cases with a slash in the name:
Going to write a shortener for this case. This will not cover the python-docs-samples case (updated link: https://github.com/GoogleCloudPlatform/python-docs-samples/issues?q=is%3Aissue+label%3A%22buildcop%3A+issue%22+dlp.inspect_content_test+) since that does not need to be grouped by the test case name -- the package name somehow needs to be pulled apart. |
@tmatsuo, do you think this is something we should change in the Build Cop Bot? Or are we good to close this for now? |
Closing this for now. Filed #550 for a more specific case. |
Is your feature request related to a problem? Please describe.
If 10 Go subtests of a single test all fail, you get 10 separate issues filed at the same time.
Describe the solution you'd like
Group subtests into a single issue. We could do this by splitting the test name on
"/"
and only keying on the first part. Not sure how this would affect other languages.Describe alternatives you've considered
Keep all of the issues separate. This is very noisy.
Additional context
https://github.com/GoogleCloudPlatform/golang-samples/issues?utf8=%E2%9C%93&q=is%3Aissue+%22bigquery%2Fsnippets%2Fquerying%3A+TestQueries%22+label%3A%22buildcop%3Aissue%22
The text was updated successfully, but these errors were encountered: