Hi Paul Many thanks for your reply. I have had a look at the logs linked on this page
https://ci.debian.net/packages/a/austin/testing/amd64/ The only version that passes is v1.0.0 and by looking at the logs of v0.7.0 and v1.0.1, which fail, it's a miracle that v1.0.0 even passes. Indeed v0.7.0 and v1.0.1 fail for the very same reason: the binary used for the tests, src/austin, is simply not there. Why it is there for the v1.0.0 I don't know, so it looks like the problem is with v1.0.0 paradoxically. This is the diff inside the debian/ folder between v1.0.0 and v1.0.1 (TLDR: only debian/austin.1, debian/changelog and debian/copyright have changed) $ git diff v1.0.0 v1.0.1 debian/ diff --git a/debian/austin.1 b/debian/austin.1 index 95a8ab0..3452e92 100644 --- a/debian/austin.1 +++ b/debian/austin.1 @@ -1,7 +1,7 @@ .\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.47.6. -.TH AUSTIN "1" "October 2019" "austin 1.0.0" "User Commands" +.TH AUSTIN "16" "May 2020" "austin 1.0.1" "User Commands" .SH NAME -austin \- manual page for austin 1.0.0 +austin \- manual page for austin 1.0.1 .SH SYNOPSIS .B austin [\fI\,OPTION\/\fR...] \fI\,command \/\fR[\fI\,ARG\/\fR...] diff --git a/debian/changelog b/debian/changelog index 6d31034..352af1a 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,10 @@ +austin (1.0.1-1) unstable; urgency=medium + + * Fixed support for Python 3.8 + + -- Gabriele N. Tornetta <phoenix1...@gmail.com> Sat, 16 May 2020 12:36:00 +0100 + + austin (1.0.0-1) unstable; urgency=medium * Added support for multi-process Python applications diff --git a/debian/copyright b/debian/copyright index 954ddfd..2f08861 100644 --- a/debian/copyright +++ b/debian/copyright @@ -4,7 +4,7 @@ Upstream-Contact: Gabriele N. Tornetta <phoenix1...@gmail.com> Source: https://github.com/P403n1x87/austin Files: * -Copyright: 2018-2019 Gabriele N. Tornetta <phoenix1...@gmail.com> +Copyright: 2018-2020 Gabriele N. Tornetta <phoenix1...@gmail.com> License: GPL-3+ License: GPL-3+ ======== This is the diff inside the test/ folder (TLDR: only a test condition has changed, but the problem is that bats cannot find the binary src/austin, so it can't even get to the point where the test logic has changed). $ git diff v1.0.0 v1.0.1 test/ diff --git a/test/test_fork_mp.bats b/test/test_fork_mp.bats index 391563b..797e0d1 100644 --- a/test/test_fork_mp.bats +++ b/test/test_fork_mp.bats @@ -18,9 +18,8 @@ invoke_austin() { echo " - Check expected number of processes." expected=3 n_procs=$( echo "$output" | sed -r 's/Process ([0-9]+);.+/\1/' | sort | uniq | wc -l ) - echo " Expected $expected and got $n_procs" - if [ $n_procs != $expected ] - then continue; fi + echo " Expected at least $expected and got $n_procs" + if [ $n_procs < $expected ]; then continue; fi echo " - Check output contains frames." if echo "$output" | grep -q "do (test/target_mp.py);L[[:digit:]]*;fact (test/target_mp.py);L" @@ -39,7 +38,7 @@ invoke_austin() { echo "================" echo echo "$output" - echo + echo false fi } ======== Hence, to the best of my knowledge, there are no changes in the debian/ area that would cause the binary in src/ to be there unless it accidentally ended up, say, in the source tarball. My next question to you is then: where is the binary supposed to be found during autopkgtest? Can I assume it will be on the PATH during testing, so that I can invoke it simply with "austin"? Or do I need to specify a precise path? Thanks for your support thus far. Cheers, Gabriele
