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

Update documentation #1533

Closed
wants to merge 2 commits into from
Closed

Update documentation #1533

wants to merge 2 commits into from

Conversation

DonggeLiu
Copy link
Contributor

No description provided.

@@ -258,7 +258,7 @@ Building benchmarks and fuzzers entails the following process:
image. This is the first image in this build process that is defined by the
main FuzzBench code (e.g. not fuzzers, benchmarks, or OSS-Fuzz). Its first
function is to copy the FuzzBench code and install packages needed to run
FuzzBench like Python3.7 For benchmarks that define a `commit` in their
FuzzBench like Python3.10. For benchmarks that define a `commit` in their
Copy link
Contributor Author

Choose a reason for hiding this comment

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

I am not sure if I understand this sentence:

  1. The original text said 3.7. I guess this is a legacy typo, as I thought the current FuzzBench requires 3.8 at minimum?
  2. Do we really need to install python in docker/benchmark-builder/Dockerfile? For example, I remove the python installation in docker/benchmark-builder/Dockerfile in Upgrade base images, benchmark images, and Python. #1526, and it still seems to be able to build libpng-1.2.56 with libfuzzer.

Copy link
Contributor

Choose a reason for hiding this comment

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

  1. Yes.
  2. We should so that there is a consistent python version used throughout the project.

Copy link
Contributor Author

@DonggeLiu DonggeLiu Oct 21, 2022

Choose a reason for hiding this comment

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

Cool, I will add back the python installation steps.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Copy link
Contributor

@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.

LGTM
Though I would have just done this documentation change in the Ubuntu upgrade and python upgrade instead of splitting it out

@DonggeLiu
Copy link
Contributor Author

LGTM Though I would have just done this documentation change in the Ubuntu upgrade and python upgrade instead of splitting it out

Good point, thanks!
I will merge this to that PR, then.

@DonggeLiu
Copy link
Contributor Author

Merged into #1526.

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