Skip to content

Commit 2bbb486

Browse files
[Chore] Add missing messages for skipping triage (#5022)
When a testcase skips opening a bug due to a similar open (or recently closed) testcase, we add a triage message to inform this on the UI. However, there were two cases that missed this message and were causing confusion to our users. This PR addresses them. Request: b/435645636
1 parent 363160d commit 2bbb486

File tree

1 file changed

+8
-1
lines changed

1 file changed

+8
-1
lines changed

src/clusterfuzz/_internal/cron/triage.py

Lines changed: 8 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -263,10 +263,17 @@ def _check_and_update_similar_bug(testcase, issue_tracker):
263263
# might be caused by non-availability of latest builds. In that case,
264264
# don't file a new bug yet.
265265
if similar_testcase.open and not similar_testcase.one_time_crasher_flag:
266+
_add_triage_message(
267+
testcase, 'Delaying filing a bug since similar reproducible testcase '
268+
f'({similar_testcase.key.id()} in issue {issue.id}) is not verified '
269+
'yet.')
266270
return True
267271

268272
# If the issue is still open, no need to file a duplicate bug.
269273
if issue.is_open:
274+
_add_triage_message(
275+
testcase, f'Skipping filing a bug since similar testcase '
276+
f'({similar_testcase.key.id()}) has an open issue ({issue.id}).')
270277
return True
271278

272279
# If the issue indicates that this crash needs to be ignored, no need to
@@ -292,7 +299,7 @@ def _check_and_update_similar_bug(testcase, issue_tracker):
292299
_add_triage_message(
293300
testcase,
294301
'Skipping filing unreproducible bug since one was already filed '
295-
f'({similar_testcase.key.id()}).')
302+
f'({similar_testcase.key.id()} in issue {issue.id}).')
296303
return True
297304

298305
# If the issue is recently closed, wait certain time period to make sure

0 commit comments

Comments
 (0)