apt/test/integration/test-apt-download-progress, branch 1.1Debians commandline package managerhttps://git.kalnischkies.de/apt/atom?h=1.12015-09-15T08:16:09Ztests: don't use hardcoded port for http and https2015-09-15T08:16:09ZDavid Kalnischkiesdavid@kalnischkies.de2015-09-14T22:33:12Zurn:sha1:6c0765c096ffb4df14169236c865bbb2b10974ae
This allows running tests in parallel.
Git-Dch: Ignore
replace direct calls to egrep with grep -E2015-08-12T09:55:47ZDaniel Hartwigmandyke@gmail.com2015-08-11T17:56:31Zurn:sha1:ad42ed4698c88e04bc242fb579f5b3e6fd9a0ee4
The rest of the initial patch is not needed or incorrect in our usage.
Big changes for the dselect scripts seem unneeded as well as those are
hardly used by anyone anymore…
[commit message written by commiter]
Closes: 255577
Thanks: David Weinehall for initial patch
fix download-file using testcases to run as root2015-06-09T10:57:36ZDavid Kalnischkiesdavid@kalnischkies.de2015-06-07T07:35:37Zurn:sha1:fec55559451dc1c440c4770ee3faa116522fc59c
Git-Dch: Ignore
Merge branch 'debian/sid' into debian/experimental2015-05-22T15:01:03ZMichael Vogtmvo@ubuntu.com2015-05-22T15:01:03Zurn:sha1:4fc6b7570c3e97b65c118b58cdf6729fa94c9b03
Conflicts:
apt-pkg/pkgcache.h
debian/changelog
methods/https.cc
methods/server.cc
test/integration/test-apt-download-progress
calculate hashes while downloading in https2015-04-18T23:13:09ZDavid Kalnischkiesdavid@kalnischkies.de2015-04-11T08:23:52Zurn:sha1:34faa8f7ae2526f46cd1f84bb6962ad06d841e5e
We do this in HTTP already to give the CPU some exercise while the disk
is heavily spinning (or flashing?) to store the data avoiding the need
to reread the entire file again later on to calculate the hashes – which
happens outside of the eyes of progress reporting, so you might ended up
with a bunch of https workers 'stuck' at 100% while they were busy
calculating hashes.
This is a bummer for everyone using apt as a connection speedtest as the
https method works slower now (not really, it just isn't reporting done
too early anymore).
test/integration/test-apt-download-progress: fix test failure on fast hardware2015-03-20T16:38:51ZMichael Vogtmvo@ubuntu.com2015-03-20T16:38:51Zurn:sha1:d01fa806061db7f5d227a0784405987c78998c84merge debian/sid into debian/experimental2015-03-16T16:59:31ZDavid Kalnischkiesdavid@kalnischkies.de2015-03-09T00:34:10Zurn:sha1:d61960d9244340956a27f4ca46aecd15cc75e18bAdd regression test for the previous commit2015-01-06T09:54:24ZMichael Vogtmvo@ubuntu.com2015-01-06T09:54:24Zurn:sha1:d13f2ef5dd2cf41d7abd7f309a9e8965a77d2a63
The issue was that https.cc never called URIStart(), one way to
detect this is that no download progress is generated without
this call. The test now checks for this and as a side-effect will
also ensure that we do not break download progress reporting and
Acquire::{http,https}::Dl-Limit accidently.