apt/debian/tests, branch 2.9.18Debians commandline package managerhttps://git.kalnischkies.de/apt/atom?h=2.9.182024-12-18T09:25:24ZIntroduce automatic pager for read commands2024-12-18T09:25:24ZJulian Andres Klodejak@debian.org2024-12-16T16:05:40Zurn:sha1:6e260e26e4cd671f781151e24d89a17b29a55530
Automatically show the output of `show`, `policy`, `list`,
`search`, `showsrc` in a pager.
The pager setup is inspired by git's pager setup. Notably,
the pager is found using APT_PAGER and PAGER variables.
We wait for the pager to be setup somewhat correctly by
using a notify pipe to figure out whether execvp() was
succesful - then the pipe will read EOF as the other end
got closed by CLOEXEC during exec - or not, then the pipe
will contain an errno.
We set up the correct handlers for signals and exit to close
the fds and wait for the pager. Notably inside the signal
handler we cannot flush our streams, only close them, so
there is some duplication.
We call the InitOutputPager() function from inside the
various Do...() functions rather than setting it up
generally in InitOutput(). Doing so allows us to first
render the progress without a pager, and then setup
the pager for the content only which improves user
experience.
When we setup a pager we also take care to disable
standard input, as we should not be prompting users
while a pager is running (the pager will be reading
from the tty directly). We do this by dup2-ing() a
/dev/null over it; if we just close()d the fd, another
open() might reuse the fd number and problems could
occur.
test: Ensure we test both gpgv-g10code and gpgv-sq2024-11-22T15:44:02ZJulian Andres Klodejulian.klode@canonical.com2024-11-22T15:20:05Zurn:sha1:e983d98c4fcd952ffcbc010b185455913c8af650tests: Temporarily disable valgrind-if-available on armhf and ppc64el2024-11-20T15:13:18ZJulian Andres Klodejulian.klode@canonical.com2024-11-20T15:11:23Zurn:sha1:b7a14e989ad1d1cef6038f85f92daef5fe90e3d6Merge branch 'json-config' into 'main'2024-11-14T14:38:32ZJulian Andres Klodejak@debian.org2024-11-14T14:38:32Zurn:sha1:8f10ee850db3892bc979694864451be3a73ad1e8
JSON: Pass options to hooks in hello message
See merge request apt-team/apt!389test: Prettify JSON tests using jq2024-11-12T13:39:22ZJulian Andres Klodejulian.klode@canonical.com2024-11-11T12:16:01Zurn:sha1:5685e944b0e9808d6f3edc9e14000c3879818ffc
This also ensures that our JSON is actually correct
JSON.
echo may fail now with EPIPE, given that it is multiline, so
wrap it in 2>/dev/null
Only run valgrind in tests if valgrind available on host2024-11-11T14:14:07Zнабnabijaczleweli@nabijaczleweli.xyz2024-11-11T14:06:27Zurn:sha1:df72264891212bc9846649f3f769a1c44fe787bftests: Add g++ dependency to pkg-config test2022-05-17T16:50:09ZJulian Andres Klodejulian.klode@canonical.com2022-05-17T16:49:33Zurn:sha1:f15178f139469b55e23133ca95facab464e2439aLink interactive helpers against system libapt for autopkgtest2022-05-07T08:45:44ZDavid Kalnischkiesdavid@kalnischkies.de2022-04-20T23:45:45Zurn:sha1:8d8b45a96ceceb015f7836cf25b99279c2f377b9
Building the library just so we can build the helpers against it is not
only wasteful but as we are supposed to test the system we can use that
as an additional simple smoke test before the real testing starts.
Avoid building inside the source dir in autopkgtest2022-05-07T08:45:44ZDavid Kalnischkiesdavid@kalnischkies.de2022-04-20T16:51:47Zurn:sha1:ee06eb541e5aa477880ff0fc575be317eccbd929
autopkgtest says:
Tests may not modify the source tree (and may not have write access to it).
We don't really modify the source of course, but we created our build/
directory in the tree, which seems to work just fine (for now), but lets
be nice.
Mark pkg-config-test autopkgtest as superficial2022-05-07T08:45:44ZDavid Kalnischkiesdavid@kalnischkies.de2022-04-20T16:42:12Zurn:sha1:a48a432223e9feb3e70b6d7dee09d035f594eeed
Reorganising the control file allows this simple test to run first and
be marked as superficial which makes no practical difference, but is
more correct.