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
When running project with docker, you should not let the tested library in the /fuzz directory(which is the working directory set by Dockerfile).
More strictly speaking, the user should keep the full path of the tested library not have words like (fuzzing|fuzz|test|OT|cre2|oss|examples), which is mentioned in the cov part of hopper file.
So if you don't notice this you will see the coverage ars zero in the report.
Since the working directory mounted by the Docker is /fuzz, the above problems are more likely to be encountered. It is best to be highlighted it in the README OR display the concrete content of -ignore-filename-regex when running llvm-cov report in the hopper script .
The text was updated successfully, but these errors were encountered:
When running project with docker, you should not let the tested library in the
/fuzz
directory(which is the working directory set by Dockerfile).More strictly speaking, the user should keep the full path of the tested library not have words like
(fuzzing|fuzz|test|OT|cre2|oss|examples)
, which is mentioned in thecov
part ofhopper
file.So if you don't notice this you will see the coverage ars zero in the report.
Since the working directory mounted by the Docker is
/fuzz
, the above problems are more likely to be encountered. It is best to be highlighted it in the README OR display the concrete content of-ignore-filename-regex
when runningllvm-cov report
in the hopper script .The text was updated successfully, but these errors were encountered: