b0cf8c021f
... but turn it back on in CI by default. The `binaryen-sys` crate builds binaryen from source, which is a drag on CI for a few reasons: * This is quite large and takes a good deal of time to build * The debug build directory for binaryen is 4GB large In an effort to both save time and disk space on the builders this commit adds a `binaryen` feature to the `wasmtime-fuzz` crate. This feature is enabled specifically when running the fuzzers on CI, but it is disabled during the typical `cargo test --all` command. This means that the test builders should save an extra 4G of space and be a bit speedier now that they don't build a giant wad of C++. We'll need to update the OSS-fuzz integration to enable the `binaryen` feature when executing `cargo fuzz build`, and I'll do that once this gets closer to landing.
22 lines
509 B
TOML
22 lines
509 B
TOML
[package]
|
|
authors = ["The Wasmtime Project Developers"]
|
|
description = "Fuzzing infrastructure for Wasmtime"
|
|
edition = "2018"
|
|
name = "wasmtime-fuzzing"
|
|
publish = false
|
|
version = "0.12.0"
|
|
|
|
[dependencies]
|
|
anyhow = "1.0.22"
|
|
arbitrary = { version = "0.4.0", features = ["derive"] }
|
|
binaryen = { version = "0.10.0", optional = true }
|
|
env_logger = "0.7.1"
|
|
log = "0.4.8"
|
|
rayon = "1.2.1"
|
|
wasmparser = "0.51.2"
|
|
wasmprinter = "0.2.1"
|
|
wasmtime = { path = "../api", version = "0.12.0" }
|
|
|
|
[dev-dependencies]
|
|
wat = "1.0.10"
|