-
Notifications
You must be signed in to change notification settings - Fork 363
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
New endpoint to create internal issues before submitting a bug #8443
base: master
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
in general I think this needs to:
- convert lines to "single tracking bugs" where it can. This would mean finding a test name and ignoring the raw error message that comes after the test name.
- keep track of the failures (job ids should be enough), primarily so when we do create the bug it will be linked properly to all the failures.
|
||
from treeherder.model.models import Bugscache, FailureLine | ||
|
||
# Only track occurences of a bug on a specific time window |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please update occurences
with occurrences
.
|
||
class InternalIssue(generics.CreateAPIView): | ||
""" | ||
Create a Bugscache entry, not necessarilly linked to a real Bugzilla ticket.µ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Remove µ
def create(self, validated_data): | ||
failure_line = validated_data["failure_line"] | ||
|
||
# TODO: Fetch all the similar failure lines |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For awareness and understanding: In general, the failure lines classified with an internal issue will be similar but they could also be different because they have a common root cause which is not logged in the failure line, e.g. a random focus issue of the browser engine or test framework can cause various form tests to fail. The canonical source for occurrences remain the classifications from Bugscache.
No description provided.