<feed xmlns='http://www.w3.org/2005/Atom'>
<title>apt/test/integration/run-tests, branch 2.7.4</title>
<subtitle>Debians commandline package manager</subtitle>
<id>https://git.kalnischkies.de/apt/atom?h=2.7.4</id>
<link rel='self' href='https://git.kalnischkies.de/apt/atom?h=2.7.4'/>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/'/>
<updated>2022-05-07T08:45:44Z</updated>
<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>
<entry>
<title>test, travis: Quieter testing with a new -qq mode</title>
<updated>2016-08-29T13:42:06Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2016-08-19T18:37:28Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=30ea7a60404ee53393235827202968393951d106'/>
<id>urn:sha1:30ea7a60404ee53393235827202968393951d106</id>
<content type='text'>
Introduce a new -qq mode for our integration test framework,
and make travis use it.

The new -qq mode sets MSGLEVEL to 1. In MSGLEVEL=1, no messages
are generated for passed tests, and all testcase filenames are
printed in the same line.

Also install first in travis, do not ls the installed output
and run the install with chronic, so we only get output if it
failed.

Gbp-Dch: ignore
</content>
</entry>
<entry>
<title>test: Allow moreutils-parallel instead of parallel</title>
<updated>2016-08-26T20:17:55Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2016-08-23T21:14:05Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=3c973af2ff85e7aae7fbdd84e7633e9d9308dde7'/>
<id>urn:sha1:3c973af2ff85e7aae7fbdd84e7633e9d9308dde7</id>
<content type='text'>
That's what it's called on FreeBSD.

Gbp-Dch: ignore
</content>
</entry>
<entry>
<title>Do not set the binary dir in run-tests, it breaks stuff</title>
<updated>2016-08-10T14:43:16Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2016-08-10T14:42:23Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=77a324fccc75b8573799a7f79ca1b3f8b0d35be7'/>
<id>urn:sha1:77a324fccc75b8573799a7f79ca1b3f8b0d35be7</id>
<content type='text'>
This breaks -j and does all sort of other weird stuff I did not
notice in the previous (non-parallel) runs.

Gbp-Dch: ignore
</content>
</entry>
<entry>
<title>test: Automatically discover CMake build directory</title>
<updated>2016-08-10T14:17:19Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2016-08-10T12:16:52Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=61fef4ddbec8f70bb9e213ac0491d4e6cfefab30'/>
<id>urn:sha1:61fef4ddbec8f70bb9e213ac0491d4e6cfefab30</id>
<content type='text'>
Look at the project root, and all directories directly below it and
pick the directory with the newest CMakeCache.txt file.

Gbp-Dch: ignore
</content>
</entry>
<entry>
<title>tests: fix parallel execution to be working dir independent</title>
<updated>2016-03-16T16:44:47Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2016-03-16T16:41:11Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=8e0c56db82fe10b0f8ceadf3187ffc672eaaff3a'/>
<id>urn:sha1:8e0c56db82fe10b0f8ceadf3187ffc672eaaff3a</id>
<content type='text'>
Git-Dch: Ignore
</content>
</entry>
<entry>
<title>tests: support spaces in path and TMPDIR</title>
<updated>2015-12-19T22:04:34Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2015-12-15T16:20:26Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=3abb6a6a1e485b3bc899b64b0a1b7dc2db25a9c2'/>
<id>urn:sha1:3abb6a6a1e485b3bc899b64b0a1b7dc2db25a9c2</id>
<content type='text'>
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
</content>
</entry>
</feed>
