apt/debian/tests, branch 2.9.15 Debians commandline package manager https://git.kalnischkies.de/apt/atom?h=2.9.15 2024-11-22T15:44:02Z test: Ensure we test both gpgv-g10code and gpgv-sq 2024-11-22T15:44:02Z Julian Andres Klode julian.klode@canonical.com 2024-11-22T15:20:05Z urn:sha1:e983d98c4fcd952ffcbc010b185455913c8af650 tests: Temporarily disable valgrind-if-available on armhf and ppc64el 2024-11-20T15:13:18Z Julian Andres Klode julian.klode@canonical.com 2024-11-20T15:11:23Z urn:sha1:b7a14e989ad1d1cef6038f85f92daef5fe90e3d6 Merge branch 'json-config' into 'main' 2024-11-14T14:38:32Z Julian Andres Klode jak@debian.org 2024-11-14T14:38:32Z urn:sha1:8f10ee850db3892bc979694864451be3a73ad1e8 JSON: Pass options to hooks in hello message See merge request apt-team/apt!389 test: Prettify JSON tests using jq 2024-11-12T13:39:22Z Julian Andres Klode julian.klode@canonical.com 2024-11-11T12:16:01Z urn: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 host 2024-11-11T14:14:07Z наб nabijaczleweli@nabijaczleweli.xyz 2024-11-11T14:06:27Z urn:sha1:df72264891212bc9846649f3f769a1c44fe787bf tests: Add g++ dependency to pkg-config test 2022-05-17T16:50:09Z Julian Andres Klode julian.klode@canonical.com 2022-05-17T16:49:33Z urn:sha1:f15178f139469b55e23133ca95facab464e2439a Link interactive helpers against system libapt for autopkgtest 2022-05-07T08:45:44Z David Kalnischkies david@kalnischkies.de 2022-04-20T23:45:45Z urn: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 autopkgtest 2022-05-07T08:45:44Z David Kalnischkies david@kalnischkies.de 2022-04-20T16:51:47Z urn: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 superficial 2022-05-07T08:45:44Z David Kalnischkies david@kalnischkies.de 2022-04-20T16:42:12Z urn: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. Try to show core dump info in test framework 2021-08-28T19:11:33Z David Kalnischkies david@kalnischkies.de 2021-04-25T20:26:42Z urn:sha1:255ec5a46aa55ad96e7dc7f9d43d5cdf71627812 If the system tells us that a core dump was created we should try to display the contained info as that system might not be easily available when we see the error (like C-I or autopkgtest). Gbp-Dch: Ignore