apt/test/integration/test-bug-598669-install-postfix-gets-exim-heavy, branch mainDebians commandline package managerhttps://git.kalnischkies.de/apt/atom?h=main2026-01-05T21:20:24Zsolver3: Rename decision to assignment2026-01-05T21:20:24ZJulian Andres Klodejak@debian.org2025-12-28T15:56:28Zurn:sha1:21d099878ed8c34f3b13747bcec380e0402e57a3
The previous use of decision here conflicted with the use
of decision level and the general notion of having made a
decision, because the assignment might have been propagated
as a matter of fact.
solver3: Allow removing manually installed packages2025-10-25T20:16:54ZJulian Andres Klodejak@debian.org2025-10-25T19:31:34Zurn:sha1:a3fca052ca21ad222ac7f2fdd7f3fe84b44beb60test: Fix some weird editing artefact2025-03-12T17:18:17ZJulian Andres Klodejulian.klode@canonical.com2025-03-12T17:17:48Zurn:sha1:5c101b3d4651b2f181ac586b088894cce5008d3bsolver3: Verbose error messages2025-03-08T22:18:05ZJulian Andres Klodejulian.klode@canonical.com2025-03-06T19:07:30Zurn:sha1:3967b75ae4a10d0d79560dfecb8eb210aad4f4f2
Introduce a new function, LongWhyStr() that returns a longer
reason for why something is being installed (or not).
This does the same path walk as the other function does, but
it renders the clauses at each level, and one per line, so
the whole output is a lot more informative.
It is a separate function to keep the existing debug messages
use the simple single line implication graph
We remove the other special case in AddWork() for empty solutions
to mke use of the general case in Solve() instead, and then adapt
the case in Solve() to the same case as in Enqueue(). This also
happens to fix the bug that when we encountered an empty clause
we just printed the clause had no solution, but not how we got
to install the package with the clause.
Adapt the test suite for the changes which is an annoying amount
of paperwork.
solver3: Extract TranslateOrGroup() out of EnqueueOrGroup()2025-02-07T19:59:43ZJulian Andres Klodejulian.klode@canonical.com2025-02-04T11:42:17Zurn:sha1:dd691af845421e6e9c6f43e51e907dd54e505604
This is not *purely* a refactoring, we accidentally used the
version of the dependency when enqueuing conflicts rather than
the reason, so the conflict string in the test case is different;
the logging had the same issue.
solver3: Use a propagation queue2025-01-30T13:50:15ZJulian Andres Klodejulian.klode@canonical.com2024-11-02T12:55:39Zurn:sha1:3523efb15d48ce3c6f9212f50dfc892497ba9dcb
Instead of directly propagating in a recursive fashion,
queue propagations in a queue and work on them in a loop
per the miniSAT paper.
We call Propagate() only at the end of the FromDepCache()
function and then in the Solve loop. Delaying the initial
propagation means that we get a stronger reasoning:
Assume you have x->a->b->c, y->c and you install x,y:
- Previously we traversed: x, y, x->a, a->b, b->c, (y->c)
- but now we traverse: x, y, x->a, y->c, a->b, (b->c)
Notably c now has the implication y->c instead of x->a->b->c.
Inside the solver we need to call Propagate in a loop:
Propagating facts can fail and we then backtrack. If backtracking
is succesful, we have gained a new fact to propagate.
test: Support the 3.0 solver in most existing test cases2024-05-24T15:01:35ZJulian Andres Klodejulian.klode@canonical.com2024-05-19T18:04:47Zurn:sha1:b5997949909ee9d5e9981c8311aea97c7b2620fd
Highlights:
- test-bug-618848-always-respect-user-requests: (Do not) Support 3.0 solver
A manually installed package is never removed just because we request
the removal of its dependency in solver3.
- test-bug-657695-resolver-breaks-on-virtuals: Support 3.0 solver
For manually installed packages, solver 3.0 would require some
new xserver-xorg-video-driver to Conflict+Replace+Provides the
old one (once the logic is implemented), but that does seem
reasonable.
- test-bug-720597-build-dep-purge: Support 3.0 solver
This needs a simple aptmark auto because pkga is removed by the
build-dep. But further adjustments are necessary because it weirdly
tested for no autoremovable packages before installing pkgc.
- test-bug-960705-*: Support 3.0 solver
Bit awkward to deal with; notably the protect to conflict doesn't
actually work anymore and that is a feature these days.
tests: support spaces in path and TMPDIR2015-12-19T22:04:34ZDavid Kalnischkiesdavid@kalnischkies.de2015-12-15T16:20:26Zurn:sha1:3abb6a6a1e485b3bc899b64b0a1b7dc2db25a9c2
This doesn't allow all tests to run cleanly, but it at least allows to
write tests which could run successfully in such environments.
Git-Dch: Ignore
test exitcode as well as string equality2015-03-16T17:01:54ZDavid Kalnischkiesdavid@kalnischkies.de2015-03-09T23:59:44Zurn:sha1:25b86db159fbc3c043628e285c0c1ef24dec2c6e
We use test{success,failure} now all over the place in the framework, so
its only consequencial to do this in the situations in which we test for
a specific output as well.
Git-Dch: Ignore
tests/integration/test-*: remove a bunch of "local" that are used outside funtions (bash complains)2010-10-13T13:22:48ZMichael Vogtmvo@debian.org2010-10-13T13:22:48Zurn:sha1:9962ae934b367294a57b27d58f7cdb4e2d54ce04