Modify readme in ossfuzz #14746
Open
Modify readme in ossfuzz #14746
Conversation
This file contains 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
|
Thank you for your contribution to the Solidity compiler! A team member will follow up shortly. If you haven't read our contributing guidelines and our review checklist before, please do it now, this makes the reviewing process and accepting your contribution smoother. If you have any questions or need our help, feel free to post them in the PR or talk to us directly on the #solidity-dev channel on Matrix. |
bshastry
reviewed
Dec 21, 2023
| @@ -6,10 +6,10 @@ | |||
|
|
|||
| We have multiple fuzzers, some based on string input and others on protobuf input. To build them, please do the following: | |||
|
|
|||
| - Create a local docker image from `Dockerfile.ubuntu.clang.ossfuzz` in the `.circleci/docker` sub-directory. Please note that this step is likely to take at least an hour to complete. Therefore, it is recommended to do it when you are away from the computer (and the computer is plugged to power since we do not want a battery drain). | |||
| - Create a local docker image from `Dockerfile.ubuntu.clang.ossfuzz` in the `solidity/scripts/docker/buildpack-deps` sub-directory. Please note that this step is likely to take at least an hour to complete. Therefore, it is recommended to do it when you are away from the computer (and the computer is plugged to power since we do not want a battery drain). If the request fails, you can replace `gcr.io/oss-fuzz-base/base-clang:latest` with `registry.aliyuncs.com/oss-fuzz-base/base-clang:latest` in `Dockerfile.ubuntu.clang.ossfuzz`. | |||
There was a problem hiding this comment.
Suggested change
| - Create a local docker image from `Dockerfile.ubuntu.clang.ossfuzz` in the `solidity/scripts/docker/buildpack-deps` sub-directory. Please note that this step is likely to take at least an hour to complete. Therefore, it is recommended to do it when you are away from the computer (and the computer is plugged to power since we do not want a battery drain). If the request fails, you can replace `gcr.io/oss-fuzz-base/base-clang:latest` with `registry.aliyuncs.com/oss-fuzz-base/base-clang:latest` in `Dockerfile.ubuntu.clang.ossfuzz`. | |
| - Create a local docker image from `Dockerfile.ubuntu.clang.ossfuzz` in the `solidity/scripts/docker/buildpack-deps` sub-directory. Please note that this step is likely to take at least an hour to complete. Therefore, it is recommended to do it when you are away from the computer (and the computer is plugged to power since we do not want a battery drain). If the request fails, you can replace `gcr.io/oss-fuzz-base/base-clang:latest` with `registry.aliyuncs.com/oss-fuzz-base/base-clang:latest` in `Dockerfile.ubuntu.clang.ossfuzz`. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
According to the new readme instruction, Ossfuzz can be successfully compiled.