Skip to content
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

Reduce bug filing threshold for libfuzzer-based Android crashes #4474

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

AashutoshMurthy
Copy link

Updated triage.py to file bugs for fuzzer crashes by lowering the threshold limit. These fuzzers run on Android platform and on libfuzzer engine.

Copy link

google-cla bot commented Dec 5, 2024

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

@svasudevprasad
Copy link
Collaborator

/gcbrun

Copy link
Collaborator

@jonathanmetzman jonathanmetzman left a comment

Choose a reason for hiding this comment

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

Can you share the rationale for this please?

src/clusterfuzz/_internal/cron/triage.py Outdated Show resolved Hide resolved
@svasudevprasad
Copy link
Collaborator

/gcbrun

@AashutoshMurthy
Copy link
Author

Can you share the rationale for this please?

This PR was created in response to the message chain on b/372321538.
To be specific, Steven's comment asked for the issue of bugs not being filed, to be fixed.
So, to not affect a large user base, we are reducing the threshold for fuzzers running on android platform and on libfuzzer engine.

def test_is_libfuzzer_android_startup_crash_1(self):
"""If this unreproducible testcase (libfuzzer) is crashing frequently,
then it is an important crash."""
self.mock.get_last_successful_hour.return_value = 417325
Copy link
Collaborator

Choose a reason for hiding this comment

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

What is the point of using this return value? I assume in production maybe it is stored as milliseconds and thus represented by an integer like this... if that is the case, please add a comment to clarify or modify the variable names to indicate such

Copy link
Author

Choose a reason for hiding this comment

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

I used this value from an existing test as reference here.

continue
# Check if the crash is a startup crash, i.e. it is causing the fuzzer
# to crash on startup and not allowing the fuzzer to run longer
if not _is_libfuzzer_android_startup_crash(testcase):
Copy link
Collaborator

Choose a reason for hiding this comment

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

Can we rearrange this logic to check that this is on the android platform. Something like:

def _is_libfuzzer_android_startup_crash(testcase): # <--- Rename to something more indicative? (ex. is_blocking_progress)
    """Checks if the given testcase is an android libfuzzer crash"""
    ...

def is_crash_important_android(testcase):
    if _is_libfuzzer_android_startup_crash:
        # important

if not _is_crash_important(testcase):
    if testcase.platform == android and not is_crash_important_android(testcase):
        continue

Copy link
Author

Choose a reason for hiding this comment

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

I have updated the logic as per your request. Please take a look.

Copy link
Collaborator

@marktefftech marktefftech left a comment

Choose a reason for hiding this comment

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

Thanks for proactively adding the tests! This is appreciated.

Left some minor comments

@AashutoshMurthy AashutoshMurthy deleted the startup_update branch December 10, 2024 19:46
@AashutoshMurthy AashutoshMurthy restored the startup_update branch December 10, 2024 19:46
@svasudevprasad
Copy link
Collaborator

/gcbrun

Updated triage.py to file bugs for fuzzer crashes by lowering the
threshold limit. These fuzzers run on Android platform and on
libfuzzer engine.
@svasudevprasad
Copy link
Collaborator

/gcbrun

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.

4 participants