<feed xmlns='http://www.w3.org/2005/Atom'>
<title>apt/test/integration/run-tests, branch 3.1.2</title>
<subtitle>Debians commandline package manager</subtitle>
<id>https://git.kalnischkies.de/apt/atom?h=3.1.2</id>
<link rel='self' href='https://git.kalnischkies.de/apt/atom?h=3.1.2'/>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/'/>
<updated>2025-02-14T18:08:45Z</updated>
<entry>
<title>test: Support comments in --skip/--only files</title>
<updated>2025-02-14T18:08:45Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2025-02-11T15:34:54Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=0c79613a5ef111ae09e1c94a2866f63fbf51c524'/>
<id>urn:sha1:0c79613a5ef111ae09e1c94a2866f63fbf51c524</id>
<content type='text'>
Strip everything after "#" and spaces before it.
</content>
</entry>
<entry>
<title>test: Fix skipping test cases</title>
<updated>2025-02-12T13:54:32Z</updated>
<author>
<name>Arnaud Rebillout</name>
<email>arnaudr@kali.org</email>
</author>
<published>2025-02-12T13:50:48Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=f67e9858fd0f12c2b8aa6ca9450cde427513d883'/>
<id>urn:sha1:f67e9858fd0f12c2b8aa6ca9450cde427513d883</id>
<content type='text'>
The `--skip` option was introduced in commit
1fbdc04be7547b8c4bb84f400329415ea0bc60b5, and it was broken straight
from the start for the case where `TESTTORUN` is not set (see last hunk
in this commit, the mistake is obvious).

It went unnoticed as the GitLab CI runs tests with the `-j` option, so
`TESTTORUN` is set. While ci.debian.net runs without -j, but doesn't
skip any test, so it doesn't trigger the bug either.
</content>
</entry>
<entry>
<title>Use sq in the test suite, remove apt-key</title>
<updated>2024-12-19T22:41:01Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2024-12-19T21:11:04Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=a00fbbdb28cc31e78882301c2efe7218583ab4cb'/>
<id>urn:sha1:a00fbbdb28cc31e78882301c2efe7218583ab4cb</id>
<content type='text'>
Remove the test case for MD5 and expired signatures, as we can't
create them (can't set signing digest, and can't set signature
expiry).

Tests for them have been added to test-method-gpgv instead.

We override sq in a function with cert-store and key-store
set to none.

This supports both sq 0.40 and sq 1.0.
</content>
</entry>
<entry>
<title>Make the failure mode for non-executable tests stronger</title>
<updated>2024-06-13T12:32:32Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2024-06-06T09:40:14Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=bfb9f2124b8f9da48b53d279278de3f8f0a00b82'/>
<id>urn:sha1:bfb9f2124b8f9da48b53d279278de3f8f0a00b82</id>
<content type='text'>
When a test-* file is created but not executable, we'd ignore
the argument and then our subprocess would run the entire
test suite itself, sequentially. Silly.

Let's just see if the file exists instead, then the test will
fail.
</content>
</entry>
<entry>
<title>test: Show statistics for parallel tests too</title>
<updated>2024-05-24T11:43:56Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2024-05-19T16:52:20Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=03f4568283205a26386584002b9ec740c55c9fb7'/>
<id>urn:sha1:03f4568283205a26386584002b9ec740c55c9fb7</id>
<content type='text'>
This makes things a bit nicer. We also include a list of passed
tests here, to use with --only to validate solver3 changes, as
well as the list of skipped tests.

But too lazy to implement these for the non-parallel case.
</content>
</entry>
<entry>
<title>test: Run working tests against the 3.0 solver</title>
<updated>2024-05-24T11:43:56Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2024-05-19T17:31:48Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=1fbdc04be7547b8c4bb84f400329415ea0bc60b5'/>
<id>urn:sha1:1fbdc04be7547b8c4bb84f400329415ea0bc60b5</id>
<content type='text'>
Implement --solver, --only, -skip flags for the test suite, and
run the test suite with the broken tests skipped against solver3.
</content>
</entry>
<entry>
<title>Ignore stty failures in testcases</title>
<updated>2022-05-07T08:45:44Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2022-04-21T10:51:20Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=e5aa5c04ecbd3cdab611794cebf9eb3aa8cbddd4'/>
<id>urn:sha1:e5aa5c04ecbd3cdab611794cebf9eb3aa8cbddd4</id>
<content type='text'>
We use 'stty sane' to combat against stepped output and co caused by
(especially) failed tests, but it does so many things that it
occasionally fails to reset some bits in the parallel interaction we
have with it which fails the tests without a real problem in apt…

Ideally we would be better at stitching the output together, but for the
time being lets ignore these failures instead to stabilize the tests.
</content>
</entry>
<entry>
<title>Use moreutils parallel even if GNU parallel is installed</title>
<updated>2022-02-02T12:18:09Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2022-01-03T10:21:12Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=794cd4a23b7cb8c0e195f8264d372203cccec8ca'/>
<id>urn:sha1:794cd4a23b7cb8c0e195f8264d372203cccec8ca</id>
<content type='text'>
GNU parallel diverts moreutils implementation away. As we us moreutils
features just installing parallel breaks the test runner hence. We have
this already for another naming scheme, so fixing this is easy enough.

Gbp-Dch: Ignore
</content>
</entry>
<entry>
<title>test suite: Do not exit 0 in trap for QUIT</title>
<updated>2017-01-24T18:19:48Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2017-01-24T18:11:30Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=bcb1919a88ea746460e623dd591f7a00135eadda'/>
<id>urn:sha1:bcb1919a88ea746460e623dd591f7a00135eadda</id>
<content type='text'>
This hides errors in the test suite because it will exit
with 0 here. Instead, just do exit 1 in most traps, and
do just the cleanup in the QUIT hook.

This fixes a regression introduced with the caching of the
GPG home directory in 4ce2f35248123ff2366c8c365ad6a94945578d66.
</content>
</entry>
<entry>
<title>tests: cache the apt-key homedir used for Release signing</title>
<updated>2016-12-21T18:36:10Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2016-12-18T16:42:17Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=4ce2f35248123ff2366c8c365ad6a94945578d66'/>
<id>urn:sha1:4ce2f35248123ff2366c8c365ad6a94945578d66</id>
<content type='text'>
Importing a new secret key into gpg(2) can be increadibly slow which
prolongs the test runs significantly – by caching the homedir we gain a
significant speedbonus as reimporting already present keys seems like a
far less costly operation.

Git-Dch: Ignore
</content>
</entry>
</feed>
