apt/test/integration/framework, branch 2.9.15Debians commandline package managerhttps://git.kalnischkies.de/apt/atom?h=2.9.152024-11-28T18:01:36ZDirectly call gpgv instead of apt-key2024-11-28T18:01:36ZJulian Andres Klodejak@debian.org2024-11-23T18:59:24Zurn:sha1:325b0c89358dae042ebfe0ba6dcbcc43253927a6test: Accept empty output from gpgv/apt-key2024-11-22T15:44:02ZJulian Andres Klodejulian.klode@canonical.com2024-11-21T19:10:47Zurn:sha1:de3f663d823f9c185514af69296d011e22161479
Our internal code always generates ENODATA for empty output and
this is checked by the previous commit, so this is entirely safe.
test: Do not fail if valgrind is not available2024-11-21T14:38:18ZJulian Andres Klodejulian.klode@canonical.com2024-11-21T14:36:59Zurn:sha1:5af5b196742a477c3effb9534c5a3257c8075a8e
The command -v check inadvertently exited 0 because it confusingly
also considers functions and aliases. Check if we are able to run
a valgrind binary instead by querying its version.
Then, the msgdebug in the alternative code path was included in the
output that we are asserting so that was causing failures too and
needs removing.
Everything is horrible :D
Only run valgrind in tests if valgrind available on host2024-11-11T14:14:07Zнабnabijaczleweli@nabijaczleweli.xyz2024-11-11T14:06:27Zurn:sha1:df72264891212bc9846649f3f769a1c44fe787bftest framework: Improve valgrind support2024-10-15T13:10:34ZJulian Andres Klodejulian.klode@canonical.com2024-10-15T13:10:34Zurn:sha1:c7dedfd7e13073c98fefbeff10b69c7512a8366e
Add support for testing apt-ftparchive, set valgrind to quiet such
that we can check program output, and pass --error-exitcode=7 to get
an (should be unused) magic error code if it detects errors.
test: Temporarily ignore autoremovable lists for solver32024-05-24T11:43:56ZJulian Andres Klodejulian.klode@canonical.com2024-05-20T11:17:35Zurn:sha1:0c700522df1c96fd591020e7b3e29bc7e36dec14
We do not show them yet, so let's ignore them so we can focus
on getting the rest of the tests to work.
test: Run working tests against the 3.0 solver2024-05-24T11:43:56ZJulian Andres Klodejulian.klode@canonical.com2024-05-19T17:31:48Zurn:sha1:1fbdc04be7547b8c4bb84f400329415ea0bc60b5
Implement --solver, --only, -skip flags for the test suite, and
run the test suite with the broken tests skipped against solver3.
solver3: Implement APT::Solver::RemoveManual to allow removing manual packages2024-05-24T11:43:56ZJulian Andres Klodejulian.klode@canonical.com2024-05-24T11:42:11Zurn:sha1:67a8a6470ddb8a603db02c5fab84aa225dc00f8d
This is mostly going to be useful for the test suite for now,
implement a function there to set it up so we can use it to
improve test suite correctness.
edsp: solver3: Show some progress2024-05-24T10:48:09ZJulian Andres Klodejulian.klode@canonical.com2024-05-19T17:32:05Zurn:sha1:4fc6affafafda1aee4cee86294ce7a2b799e2799
Ignore the Solving dependencies... line in the testing framework
for compatibility with the existing test cases.
Fix accidental silencing of output differences in tests2024-05-16T11:10:34ZDavid Kalnischkiesdavid@kalnischkies.de2024-05-16T11:10:34Zurn:sha1:15f7214fa2144eeff5ada93e680acd368e9e763a
Removing every line with at least three characters at the end makes
comparisons for output differences rather easy to pass. The intend
was to match for '\.\.\.' but given we have to adapt the strings to
include autoremove remarks we can also include the string that appeared
now that state information is provided (in the form of autobits).
Regession-Of: 734eb9ac3f65e38ac3ba7f2d50ea206743a6f611