-
Notifications
You must be signed in to change notification settings - Fork 54
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
Introspector not showing coverage on Python Decorators #1003
Comments
Do I get this right, that the decorator is recognised in the calltree and the coverage is recorded in |
Ah thanks, I will see if I can go over this Monday! |
Fixes: #1003 Signed-off-by: David Korczynski <[email protected]>
Should be fixed in #1005 Thanks for reporting! |
leaving open until we've bumped oss-fuzz |
Thanks for the quick fix. Did a bit of local testing with the latest fuzz-introspector repo and results look good.
|
Hey @DavidKorczynski , some observations from the latest introspector report for cachetools https://storage.googleapis.com/oss-fuzz-introspector/cachetools/inspector-report/20230501/fuzz_report.html . The calltree looks good, and However the overall "functions statically reachable" and "cyclomatic complexity statically reachable" overview numbers haven't changed. Is there a secondary fix needed on the introspector get the |
I recently integrated the cachetools library into OSS-Fuzz recently. This library uses a
@cached
decorator to indicate a function output to cache, e.g.I can't get the introspector to recognise that we're hitting the
cached
decorator. I can see the coverage here cachetools/__init__py.html:632 but I can't get it in the call graph.Some other data points, if you see fuzzerLogFile-fuzz_cached.data.yaml this method is on line
629
CallTree File fuzzerLogFile-fuzz_cached.data
And Coverage File all_cov.json
Any idea if this is an introspector issue, or if it's likely something else?
The text was updated successfully, but these errors were encountered: