apt/test/integration/test-apt-ftparchive-cachedb, branch mainDebians commandline package managerhttps://git.kalnischkies.de/apt/atom?h=main2025-02-27T12:26:14Ztest-apt-ftparchive-cachedb: Avoid race condition in test case2025-02-27T12:26:14ZJulian Andres Klodejulian.klode@canonical.com2025-02-27T12:26:14Zurn:sha1:b2d534b458f911eba7b4b0d71ae2ae31174ced32
apt-ftparchive skips regenerating Contents if they are newer than
the Packages files. Most of the time, the test ended up generating
Contents and Packages files with the same-second timestamp; so we
ended up regenerating them and passing the test.
However, sometimes, the timestamp of the Contents file was 1s
higher and we ended up not regenerating the Contents file and
hence failed the test case.
Ensure the timestamps actually are the same to avoid the race
condition and make this stable.
ftparchive: writer: Remove line length limit on file lists2024-11-20T14:04:28ZJulian Andres Klodejulian.klode@canonical.com2024-11-11T13:06:22Zurn:sha1:918a13883a6d657bba2b9d786a9468332ab0f06e
LP: #2087848
ftparchive: cachedb: Remove 600-byte key limit2024-11-20T14:04:28ZJulian Andres Klodejulian.klode@canonical.com2024-11-11T13:09:41Zurn:sha1:709adda89a575e6c542310e6632c090632bb9732
Instead of snprintf() into a fixed-size buffer, construct an
std::string using assign() and append().
A previous version used strprintf() which would have been
hilariously inefficient.
LP: #2087848
ftparchive: override: Remove fixed-size line buffers2024-11-18T20:11:18ZJulian Andres Klodejulian.klode@canonical.com2024-11-11T12:53:59Zurn:sha1:b888c66c7244de9b20d174555ffdc22829d6c222
LP: #2087848
fix various typos reported by spellintian2017-01-19T14:59:38ZDavid Kalnischkiesdavid@kalnischkies.de2017-01-19T14:14:19Zurn:sha1:93cff633a830e222693fc0f3d78e6e534d1126ee
Most of them in (old) code comments. The two instances of user visible
string changes the po files of the manpages are fixed up as well.
Gbp-Dch: Ignore
Reported-By: spellintian
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
tests: use quiet level 0 by default in tests2015-11-19T16:13:56ZDavid Kalnischkiesdavid@kalnischkies.de2015-11-19T15:00:33Zurn:sha1:87d6947d51717e8b0e975d913986161598a7259a
Git-Dch: Ignore
tests: collect more details about failed checkdiffs2015-09-02T09:31:32ZDavid Kalnischkiesdavid@kalnischkies.de2015-09-02T09:31:32Zurn:sha1:22ac12b2c4060aa4dbbb2da07f4191d966738103
Git-Dch: Ignore
sync TFRewrite*Order arrays with dpkg and dak2015-05-11T15:22:32ZDavid Kalnischkiesdavid@kalnischkies.de2015-05-09T16:55:41Zurn:sha1:e8fb1cdfdd13e45f2b3abbd57a28b57ae6137f14
dpkg and dak know various field names and order them in their output,
while we have yet another order and have to play catch up with them as
we are sitting between chairs here and neither order is ideal for us,
too.
A little testcase is from now on supposed to help ensureing that we do
not derivate to far away from which fields dpkg knows and orders.
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