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

Make /out be a link to the actual build directory on CF. #162

Closed
oliverchang opened this issue Dec 9, 2016 · 3 comments
Closed

Make /out be a link to the actual build directory on CF. #162

oliverchang opened this issue Dec 9, 2016 · 3 comments
Assignees

Comments

@oliverchang
Copy link
Collaborator

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.

@oliverchang oliverchang self-assigned this Dec 9, 2016
@oliverchang
Copy link
Collaborator Author

Should work now.

@oliverchang
Copy link
Collaborator Author

Reopening this, since this won't work as expected since in:

https://github.com/google/oss-fuzz/blob/master/infra/libfuzzer-pipeline.groovy#L101

We do zip -j ... (and without -r).

@inferno-chromium
Copy link
Collaborator

This can be closed now.

DavidKorczynski pushed a commit that referenced this issue Jul 9, 2024
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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants