aboutsummaryrefslogtreecommitdiff
path: root/docs/getting-started/new_project_guide.md
diff options
context:
space:
mode:
authorMax Moroz <mmoroz@chromium.org>2020-03-06 07:54:33 -0800
committerMax Moroz <mmoroz@chromium.org>2020-03-06 07:54:33 -0800
commit072457fd3c8529c8b7ea474959175fb26158a2cc (patch)
tree886a34d0cea2868bd6a6ac074db83d8ec1048860 /docs/getting-started/new_project_guide.md
parent56dc446432a6ede210431aca2a86a76dff57c60b (diff)
downloadoss-fuzz-072457fd3c8529c8b7ea474959175fb26158a2cc.tar.gz
[docs] Increase the documented disk size on the builder (caused confusion in #3382).
Diffstat (limited to 'docs/getting-started/new_project_guide.md')
-rw-r--r--docs/getting-started/new_project_guide.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/getting-started/new_project_guide.md b/docs/getting-started/new_project_guide.md
index 8018c6052..fec67c936 100644
--- a/docs/getting-started/new_project_guide.md
+++ b/docs/getting-started/new_project_guide.md
@@ -258,7 +258,7 @@ See the [Provided Environment Variables](https://github.com/google/oss-fuzz/blob
## Disk space restrictions
-Our builders have a disk size of 70GB (this includes space taken up by the OS). Builds must keep peak disk usage below this.
+Our builders have a disk size of 250GB (this includes space taken up by the OS). Builds must keep peak disk usage below this.
In addition, please keep the size of the build (everything copied to `$OUT`) small (<10GB uncompressed). The build is repeatedly transferred and unzipped during fuzzing and runs on VMs with limited disk space.