Skip to content

[Tracing] Emiting TestcaseRejectionEvent during triage #4827

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

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

vitaliset
Copy link
Collaborator

This PR introduces the emits of TestcaseRejectionEvent in the desired steps of the triage task life cycle as stated in the "Testcase rejection" section of "Lightweight Clusterfuzz Tracing" doc.

We are also adding assertions for verification of the emit.

The other remaining cases where TestcaseRejectionEvent must be emitted (namely fuzz task and corpus pruning) will be addressed in separate PRs.

b/394056013

@ViniciustCosta
Copy link
Collaborator

I will do a full review later, but just a heads up to avoid merging this one before actually testing it, since it touches critical part of the code (triage).

@@ -262,10 +263,20 @@ def _check_and_update_similar_bug(testcase, issue_tracker):
# might be caused by non-availability of latest builds. In that case,
# don't file a new bug yet.
if similar_testcase.open and not similar_testcase.one_time_crasher_flag:
events.emit(
Copy link
Collaborator

@vitorguidi vitorguidi Jun 13, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Now that I think of it, this event will be emited multiple times until the testcase itself is marked as closed, or something else that prevents it from entering this triage loop indefini.

It is not as simple as it looked from the start, we need to check the cleanup code to understand if that might be correct place to emit

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

vitaliset added a commit that referenced this pull request Jun 15, 2025
While writing #4827, I realized this pattern might be a better way of
asserting the emits (which is pretty similar to what we are doing in
`events_test.py` anyway).

Co-authored-by: Carlo Lemos <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants