-
Notifications
You must be signed in to change notification settings - Fork 566
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
Handle disfunctional issue handlers properly in triage #4476
Conversation
This reverts commit 64470a0.
continue | ||
|
||
# If this project does not have an associated issue tracker, we cannot | ||
# file this crash anywhere. | ||
issue_tracker = issue_tracker_utils.get_issue_tracker_for_testcase(testcase) | ||
try: |
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.
This is the part that solves the incident, along deleting the config
@jonathanmetzman
continue | ||
|
||
# Clean up old triage messages that would be not applicable now. | ||
testcase.delete_metadata(TRIAGE_MESSAGE_KEY, update_testcase=False) | ||
|
||
# File the bug first and then create filed bug metadata. | ||
# # File the bug first and then create filed bug metadata. |
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.
extra
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.
lgtm
Fuchsia testcases were referencing monorail, for which the API was deprecated. This implied on the cronjob failing prematurely, and no issues being filed on google3. This PR adds extra logging, so we can troubleshoot this sort of issue more easily. Also, under the triage cronjob, the ValueError exception is handled, to handle gracefully the case where some testcase references an issue finder that is not present under the issue tracker config.
Motivation
Fuchsia testcases were referencing monorail, for which the API was deprecated. This implied on the cronjob failing prematurely, and no issues being filed on google3.
This PR adds extra logging, so we can troubleshoot this sort of issue more easily.
Also, under the triage cronjob, the ValueError exception is handled, to handle gracefully the case where some testcase references an issue finder that is not present under the issue tracker config.