You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 30, 2021. It is now read-only.
When attempting to run our fuzz test suite remotely all of our jobs are failing with the following message:
020/02/25 14:18:11 Running fuzzing with: [-jar zest-cli.jar --exit-on-crash --exact-crash-path=artifact --libfuzzer-compat-output fuzzer -rss_limit_mb=1984 com.github.nitram509.jmacaroons.FuzzTests macaroonSerialization]
FUZZER: Unknown option: '-rss_limit_mb=1984'
FUZZER: Usage: ZestCLI [[-e] [--exact-crash-path=<exactCrashPath>]] [[-e]
FUZZER: [--exact-crash-path=<exactCrashPath>]] [-hlV]
FUZZER: [-i=<inputDirectory>] [-o=<outputDirectory>] PACKAGE TEST_CLASS
FUZZER: TEST_METHOD
FUZZER: PACKAGE package containing the fuzzer and all dependencies
FUZZER: TEST_CLASS full class name where the fuzz function is located
FUZZER: TEST_METHOD fuzz function name
FUZZER: -e, --exit-on-crash Exit fuzzer on first crash (default: false)
FUZZER: --exact-crash-path=<exactCrashPath>
FUZZER: exact path for the crash
FUZZER: -h, --help Show this help message and exit.
FUZZER: -i, --input=<inputDirectory>
FUZZER: Input directory containing seed test cases (default:
FUZZER: none)
FUZZER: -l, --libfuzzer-compat-output
FUZZER: Use libFuzzer compat output instead of AFL like stats
FUZZER: screen (default: false)
FUZZER: -o, --output=<outputDirectory>
FUZZER: Output Directory containing results (default:
FUZZER: fuzz_results)
FUZZER: -V, --version Print version information and exit.
2020/02/25 14:18:12 process finished with error = exit status 2
2020/02/25 14:18:12 Exit Status: 2
I can confirm the suite runs locally, but I'm not sure how to work around this issue using the fuzzit dashboard.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When attempting to run our fuzz test suite remotely all of our jobs are failing with the following message:
I can confirm the suite runs locally, but I'm not sure how to work around this issue using the fuzzit dashboard.
The text was updated successfully, but these errors were encountered: