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
https://github.com/plasma-umass/slipcover - if the overhead of adding instrumentation is low, this could be a big win - and amortized across many unlikely-to-find-new-branches executions anyway if not. Note that we don't want to remove the instrumentation once hit, since we collect coverage for each test case.
The text was updated successfully, but these errors were encountered:
As of 25.01.2, we now use sys.monitoring for coverage on 3.12+! Slipcover could still provide significant speedups for older versions, but is currently low priority as supporting another coverage-measurement interface would increase complexity.
tybug
changed the title
Try slipcover for coverage measurement, and sys.monitoring (in py3.12+)
Try slipcover for coverage measurement on <= py3.11Jan 24, 2025
https://github.com/plasma-umass/slipcover - if the overhead of adding instrumentation is low, this could be a big win - and amortized across many unlikely-to-find-new-branches executions anyway if not. Note that we don't want to remove the instrumentation once hit, since we collect coverage for each test case.
The text was updated successfully, but these errors were encountered: