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
For various reasons, the directory containing the fuzzer build on CF can't be hardcoded. However, we can link /out to this directory so fuzz targets can hardcode paths to data files etc.
The text was updated successfully, but these errors were encountered:
FI has updated benchmarks, this PR updates the YAML files accordingly.
This is discovered by @trashvisor, because some function signatures in
YAML files are different from the ones expected by FI APIs.
Also cherrypicked #158, please let me know if I missed any.
---------
Co-authored-by: Oliver Chang <oliverchang@users.noreply.github.com>
For various reasons, the directory containing the fuzzer build on CF can't be hardcoded. However, we can link /out to this directory so fuzz targets can hardcode paths to data files etc.
The text was updated successfully, but these errors were encountered: