Release v3.6.0 #205
Release v3.6.0 #205
Commits on Oct 4, 2023
-
-
ci(benchmarks): improve benchmark reporting
This change improves the report from benchmark runs by adding t-tests for each scenario. This allows the benchmarks to provide a summary at the end with the scenarios that are likely to show perfomance difference between the latest released version and the one that comes with the PR the benchmarks run for. This also updates the versions that are being benchmarked to include the latest releases.
-
ci: add data validation workflow
This change adds a data validation workflow. Data is validated by performing a Hotelling T2 test on the collected data.
-
This change adds extra steps to the CI workflows to build Python wheels so that the Austin binary can be installed with pip from PyPI.
-
refactor: use proper lasti formula for 3.11
Use the more correct expression for computing the lasti index with Python 3.11.
-
-
ci(checks): build cppcheck from sources
The version of cppcheck available from the package manager tends to be outdated. In this change we build from sources instead. We cache the build result for faster execution.
-
fix(macos): report permission error if not root
This change ensures that Austin reports the expected error code and message when running without the superuser privileges.
-
-
fix: version detection on Python 3.11
The wrong symbol name was being used on OSX, preventing the inference of the Python version from symbols.
-
-
chore: drop support for old Python versions
Python < 3.8 is no longer maintained, so we drop support for it. Previous versions of Austin can still be used if needed.
-
-
-
chore: reduce tracked binary symbols
Since we no longer support CPython < 3.8, we drop the tracking of symbols that are no longer exported by the CPython binaries in later versions. We also rationalise the error propagation for a more robust error handling and propagation logic.
-
-
-
-
-
-
-
tests: run uwsgi tests in virtual environment
We run the uwsgi tests in separated virtual environment to ensure that we install it using the interpreter that Austin is being tested against. Currently, we install the dependency in the environment used to run pytest, which means that we test uwsgi with the same Python version in every job.
-
-
-
ci: bump GitHub action versions
We bump the checkout action version from 2 to 3, and setup-python from 2 to 4 (the latest at the time this change is being made) to resolve the node12 deprecation warnings.
-
ci: run certain workflows when necessary
We add path filtering to some GitHub workflows so that they are triggered when necessary.
-
We group tests in categories to allow for better fine-graining when running the suite.
-
-
We try to collect core dump on Linux once more
-
-
-
-
-
docs: add missing link to Anaconda
We also improve the wording of MacOS compatibility to explicitly mention limitations with code-signing.
-
We add more details to the logs generated by Austin on Windows to include a timestamp and process information. This allows us to collect the data in tests for helping with investigations.
-
-
chore: set error in run method
To ensure that we get the expected exit code and error messages, we set the correct error in the internal _py_proc__run method on the fail paths
-
-
chore: remove VM bounds tracking logic
With the removal of the heap scanning logic, we no longer need to keep track of VM bounds so we remove the relevant code.
-
-
fix(austinp): ensure threads are resumed on sampling errors
We make sure that threads are resumed regardless of potential errors during the sampling of the threads.
-
chore: return negated signal number on signal
We make sure that we handle signals and propagate the signal number as exit code. We negate the number to distinguish it from Austin error codes.
-
fix: propagate signals to spwned process
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.
-
-
chore(linux): guard against potentially null map
A segmentation fault was caught in CI exposing a missing NULL check on a local variable in recently-added code. We add a check to prevent this from happening.
-
ci(benchmarks): run only the last release
We speed up the benchmarks CI run by only running the latest release and dev. Any issues caught in this way can be analysed locally if needed.
-
docs: update documentation source for 3.6 release
The documentation sources are updated to include mention of the CPython 3.12 support and other features that are shipped with the upcoming 3.6 release of Austin.
-
-
