apt/test/integration/framework, branch 1.2_exp1Debians commandline package managerhttps://git.kalnischkies.de/apt/atom?h=1.2_exp12016-01-08T14:40:01Ztests: limit autotest-functionname generation to sane characters2016-01-08T14:40:01ZDavid Kalnischkiesdavid@kalnischkies.de2016-01-08T12:08:19Zurn:sha1:896f0ae857b693782658145e16e21a3054dd5280
Some (older) versions of bash seem to be allergic to a method named
"aptautotest_grep_^apt" (note the caret). Unlikely that we are going to
write autotests for such commands so we could just skip those, but lets
instead just use "normal" characters in the names and strip the rest as
we already did with the (arguable more common) '-'.
support '-' and no parameter for stdin in apt-helper cat-file2016-01-08T14:40:01ZDavid Kalnischkiesdavid@kalnischkies.de2016-01-07T23:35:39Zurn:sha1:abec2980ef1ff051be14c26097a76b6429b3b7bc
This way it works more similar to the compressor binaries, which we
can relief in this way from their job in the test framework avoiding the
need of adding e.g. liblz4-tool to the test dependencies.
keep compressed indexes in a low-cost format2016-01-08T14:40:01ZDavid Kalnischkiesdavid@kalnischkies.de2016-01-07T19:32:09Zurn:sha1:0179cfa83cf0042235eda41db7f35c420781c63e
Downloading and storing are two different operations were different
compression types can be preferred. For downloading we provide the
choice via Acquire::CompressionTypes::Order as there is a choice to
be made between download size and speed – and limited by whats available
in the repository.
Storage on the other hand has all compressions currently supported by
apt available and to reduce runtime of tools accessing these files the
compression type should be a low-cost format in terms of decompression.
apt traditionally stores its indexes uncompressed on disk, but has
options to keep them compressed. Now that apt downloads additional files
we also deal with files which simply can't be stored uncompressed as
they are just too big (like Contents for apt-file). Traditionally they
are downloaded in a low-cost format (gz) as repositories do not provide
other formats, but there might be even lower-cost formats and for
download we could introduce higher-cost in the repositories.
Downloading an entire index potentially requires recompression to
another format, so an update takes potentially longer – but big files
are usually updated via pdiffs which has to de- and re-compress anyhow
and does it on the fly anyhow, so there is no extra time needed and in
general it seems to be benefitial to invest the time in update to save
time later on file access.
tests: try to pick up compressors from config automatically2016-01-08T14:40:01ZDavid Kalnischkiesdavid@kalnischkies.de2016-01-03T21:39:46Zurn:sha1:912a61312a0463b46d6560756c89146f59daaab6
Less hardcoding should help while introducing new compressors.
Git-Dch: Ignore
tests: support gpg2 properly in all testcases2015-12-19T22:04:34ZDavid Kalnischkiesdavid@kalnischkies.de2015-12-18T12:17:11Zurn:sha1:785cb6fc843f4751ff9c57dcdf375ad061e83f36
The output changes slightly between different versions, which we already
dealt with in the main testcase for apt-key, but there are two more
which do not test both versions explicitly and so still had gpg1 output
to check against as this is the default at the moment.
Git-Dch: Ignore
avoid evaluating shell in paths used in apt-key2015-12-19T22:04:34ZDavid Kalnischkiesdavid@kalnischkies.de2015-12-17T16:41:11Zurn:sha1:bc8f83a5afd858206efe518c31bbb1ac948a39a3
apt-key creates internally a script (since ~1.1) which it will call to
avoid dealing with an array of different options in the code itself, but
while writing this script it wraps the values in "", which will cause
the shell to evaluate its content upon execution.
To make 'use' of this either set a absolute gpg command or TMPDIR to
something as interesting as:
"/tmp/This is fü\$\$ing cràzy, \$(man man | head -n1 | cut -d' ' -f1)\$!"
If such paths can be encountered in reality is a different question…
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 framework: More noopchroot fixes2015-12-14T12:40:39ZJulian Andres Klodejak@debian.org2015-12-14T12:39:52Zurn:sha1:950733c947acd50afe498e900954d911454c57e7
Use asprintf() so we have easy error detection and do not depend
on PATH_MAX.
Do not add another separator to the generated path, in both cases
the path inside the chroot is guaranteed to have a leading /
already.
Also pass -Wall to gcc.
test framework: Unset no_proxy as well2015-12-14T12:33:55ZJulian Andres Klodejak@debian.org2015-12-14T12:33:55Zurn:sha1:59f57473ab85d3fb3354d086db2df2466c1c3896
This caused test-bug-717891-abolute-uris-for-proxies to fail
Gbp-Dch: ignore
test framework: Unset http proxy variables in setupenvironment2015-12-14T12:27:34ZJulian Andres Klodejak@debian.org2015-12-14T12:27:00Zurn:sha1:1ba0302352b320108b3ca23130ceca1d46f0a999
This breaks a lot of test cases
Gbp-Dch: ignore