[wasm] Pulling in new wasm function fuzzer, and wasm module corpus.

DEPS

 # This file is used to manage the dependencies of the Chromium src repo. It is
 # used by gclient to determine what version of each dependency to check out, and
 # where.
 #
 # For more information, please refer to the official documentation:
 #   https://sites.google.com/a/chromium.org/dev/developers/how-tos/get-the-code
 #
 # When adding a new dependency, please update the top-level .gitignore file
 # to list the dependency's destination directory.
 #
@@ skipping 983 matching lines @@
     'action': ['python', 'src/third_party/instrumented_libraries/scripts/download_binaries.py'],
   },
   {
     # Pull doclava binaries if building for Android.
     'name': 'doclava',
     'pattern': '.',
     'action': ['python',
                'src/build/android/download_doclava.py',
     ],
   },
+  {
+    "name": "wasm_fuzzer",

[Nico, 2016/09/09 20:43:10]

Do we really need to pull this on every single checkout? I'd imagine that almost
nobody uses this.

[Nico, 2016/09/15 19:40:39]

^ Ping?

[ahaas, 2016/09/16 08:02:56]

These files are the seed corpus of the v8-wasm-fuzzer which are needed to give
clusterfuzz some initial guidance. Since the files are binary we do not want to
add them to the repository because they are hard to review and to modify.
Downloading these files from google storage was the best solution we could come
up with which provides clusterfuzz with a seed corpus and keeps binary files out
of the repository.

[bradn, 2016/09/16 22:37:55]

kcc, mmoroz, does this need to actually be in chrome checkouts for you guys to
use it as an updated fuzzer corpus?

[mmoroz, 2016/09/17 17:35:26]

We have an alternative way to provide the corpus
(https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/eff...),
but using the repo is our preferred way.

I agree that requiring everybody with Chromium checkout to execute that is an
overhead. Since your corpus is not directly stored in Chromium repo (I mean we
don't track changes for the files itself, etc), I believe that we have to use
clusterfuzz-corpus GCS bucket.

How frequent do you update these files? Should we set up anything special to
update them on ClusterFuzz automatically?

+    "pattern": ".",
+    "action": [ "download_from_google_storage",
+                "--no_resume",
+                "--no_auth",
+                "-u",
+                "--bucket", "v8-wasm-fuzzer",
+                "-s", "src/v8/test/fuzzer/wasm.tar.gz.sha1",
+    ],
+  },
+  {
+    "name": "wasm_asmjs_fuzzer",
+    "pattern": ".",
+    "action": [ "download_from_google_storage",
+                "--no_resume",
+                "--no_auth",
+                "-u",
+                "--bucket", "v8-wasm-asmjs-fuzzer",
+                "-s", "src/v8/test/fuzzer/wasm_asmjs.tar.gz.sha1",
+    ],
+  },
 ]
 
 # ANGLE manages DEPS that it also owns the build files for, such as dEQP.
 recursedeps = [("src/third_party/angle", "DEPS.chromium")]