-
Notifications
You must be signed in to change notification settings - Fork 628
Ensure rss_limit_mb is set to 0 for all Chromium/Google tasks
#5466
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
tbantikyan
wants to merge
6
commits into
master
Choose a base branch
from
ensure-no-memory-limit
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
be55e5d
Ensure `rss_limit_mb` is set to 0 for all Chromium tasks
tbantikyan 6b42d73
Address initial review feedback
tbantikyan 7722ec3
revert argument setting and use @patch for test
tbantikyan 852c50e
Merge branch 'master' into ensure-no-memory-limit
tbantikyan 3c261ff
Update _add_rss_limit_if_missing to return input if rss_limit exists
tbantikyan 015671d
Add bug for tracking minimize_testcase FIXME
tbantikyan File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Some comments aren't visible on the classic Files Changed page.
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
IIUC, this gets the current arguments for the fuzzer. Does that mean this would return
timeout_per_input? If so, we probably want to override it like we do in the reproduce task.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.
Yes, it does return
timeout_per_input. I'm thinking it makes more sense to delete the argument than to do what reproduce is doing. In deleting, we are preserving the functionality that existed before this CL, as thetimeout_per_inputvalue is not set in this method. Also, I think that changing environment variables is a little like working with global variables and makes the code harder to reason about, so I'd prefer to avoid it.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.
Do you know what libfuzzer does for the minimize task? Does it set a value for TIMEOUT_PER_INPUT? If so, we should probably copy that.
Ah, sorry for the confusion. I didn't mean to say we should use environment variables, I more meant we should replace with
TIMEOUT_PER_INPUT_REPR_DEFAULTorTEST_TIMEOUTthe same wayreproducedoes. IIUC, if we don't set the flag we would use the default value from centipede which might not be the correct one depending on TEST_TIMEOUT and TIMEOUT_PER_INPUT_REPR_DEFAULT.IIUC,
reproduceuses environment variables because it's not runningcentipede --binary; it's running the binary directly e.g.foo_fuzzerand the only way to pass arguments to centipede in that case is through environment variables.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.
libFuzzer's
minimize_testcasemethod just passes through the arguments passed to it, but IIUC a timeout is typically present from the testcase. I'm hesitant to handle timeout logic now since it's not entirely relevant to the PR. I could open a bug and look into, alongside theFIXME, in another PR if that would make sense.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.
If it's passing through
argumentsthen they are the arguments from the database. Not all arguments are stored in the DB as is, so it might be removing it or setting something different.Anyway, I think leaving a FIXME is ok. This method is never called anyway :/