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

Upload crashes to logs bucket in permissionless way #4400

Merged
merged 10 commits into from
Nov 14, 2024
Merged

Conversation

jonathanmetzman
Copy link
Collaborator

@jonathanmetzman jonathanmetzman commented Nov 12, 2024

This puts crashes in the output for uploading. That can probably be replaced with a signed_url.
It can probably be improved if the crash is included elsewhere.

@jonathanmetzman jonathanmetzman merged commit 5d59e5c into master Nov 14, 2024
7 checks passed
@jonathanmetzman jonathanmetzman deleted the fuzzperm2 branch November 14, 2024 02:14
if crash_path is None:
return engine_output
if os.path.getsize(crash_path) > 10 * 1024**2:
return engine_output
Copy link
Collaborator

Choose a reason for hiding this comment

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

should we log an error ? this seems pretty bad if we're not uploading a testcase right?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

It's just a testcase in logs. Really not that important.

@@ -534,7 +535,7 @@ def _do_run_testcase_and_return_result_in_queue(crash_queue,
# Don't upload uninteresting testcases (no crash) or if there is no log to
# correlate it with (not upload_output).
if upload_output:
upload_testcase(file_path, log_time)
upload_testcase(file_path, log_time, None)
Copy link
Collaborator

Choose a reason for hiding this comment

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

wrong order of arguments?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Youre right.
I think because of how many edge cases our code has there's no actual misbehavior resulting from this bug

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

WIll fix in another PR.

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.

2 participants