Closed P403n1x87 closed 1 year ago
Patch coverage: 72.72%
and project coverage change: -0.09%
:warning:
Comparison is base (
7dbb39a
) 68.38% compared to head (75246e4
) 68.29%. Report is 1 commits behind head on devel.:exclamation: Current head 75246e4 differs from pull request most recent head ce3c2de. Consider uploading reports for the commit ce3c2de to get more accurate results
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
Running Austin benchmarks with Python 3.10.13
Comparison of dev against 3.5.0.
The following scenarios show a statistically significant difference in performance between the two versions.
Sample Rate | Saturation | Error Rate | Sampling Speed | |
---|---|---|---|---|
RSA keygen [sampling interval: 1] | :green_circle: | :yellow_circle: | :yellow_circle: | :green_circle: |
Full metrics [sampling interval: 1] | :yellow_circle: | :yellow_circle: | :green_circle: | :yellow_circle: |
Multiprocess wall time [sampling interval: 1] | :red_circle: | :yellow_circle: | :yellow_circle: | :red_circle: |
Multiprocess wall time [sampling interval: 10] | :red_circle: | :yellow_circle: | :yellow_circle: | :red_circle: |
Description of the Change
When Austin is given a command to launch, we make sure that any termination signal that Austin receives is propagated to the spawned process to prevent it from running potentially indefinitely in the background.
Regressions
We don't expect any tools based on Austin to rely on the previous behaviour, so we do not expect any regressions.
Verification Process
This bug was caught with the austin-python test suite.