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

[fuzz] Configure the differential target #4773

Merged
merged 5 commits into from
Aug 24, 2022

Commits on Aug 24, 2022

  1. [fuzz] Configure the differential target

    This change is a follow-on from bytecodealliance#4515 to add the ability to configure
    the `differential` fuzz target by limiting which engines and modules are
    used for fuzzing. This is incredibly useful when troubleshooting, e.g.,
    when an engine is more prone to failure, we can target that engine
    exclusively. The effect of this configuration is visible in the
    statistics now printed out from bytecodealliance#4739.
    
    Engines are configured using the `ALLOWED_ENGINES` environment variable.
    We can either subtract from the set of allowed engines (e.g.,
    `ALLOWED_ENGINES=-v8`) or build up a set of allowed engines (e.g.,
    `ALLOWED_ENGINES=wasmi,spec`), but not both at the same time.
    `ALLOWED_ENGINES` only configures the left-hand side engine; the
    right-hand side is always Wasmtime. When omitted, `ALLOWED_ENGINES`
    defaults to [`wasmtime`, `wasmi`, `spec`, `v8`].
    
    The generated WebAssembly modules are configured using
    `ALLOWED_MODULES`. This environment variables works the same as above
    but the available options are: [`wasm-smith`, `single-inst`].
    abrown committed Aug 24, 2022
    Configuration menu
    Copy the full SHA
    62061a8 View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    5958292 View commit details
    Browse the repository at this point in the history
  3. Configuration menu
    Copy the full SHA
    13bda67 View commit details
    Browse the repository at this point in the history
  4. review: use &str in signatures

    abrown committed Aug 24, 2022
    Configuration menu
    Copy the full SHA
    737f860 View commit details
    Browse the repository at this point in the history
  5. Configuration menu
    Copy the full SHA
    9a9df12 View commit details
    Browse the repository at this point in the history