apt/test/libapt/srvrecs_test.cc, branch 1.3_rc1Debians commandline package managerhttps://git.kalnischkies.de/apt/atom?h=1.3_rc12015-09-14T13:22:18Zsrv test: do 100 pulls twice and compare list2015-09-14T13:22:18ZDavid Kalnischkiesdavid@kalnischkies.de2015-09-11T23:23:01Zurn:sha1:9bfb1136abfd58e48545304507dedceb2fe87a36
The previous implementation was still a bit unstable in terms of failing
at times. Lets try if we have more luck with this one.
Git-Dch: Ignore
use clock() as source for SRV randomness2015-09-01T17:01:45ZDavid Kalnischkiesdavid@kalnischkies.de2015-09-01T16:32:22Zurn:sha1:76abe9a5aad69eb7e67295588c6825cdae0341af
Initializing a random number generator with the time since epoch could
be good enough, but reaches its limits in test code as the 100
iterations might very well happen in the same second and hence the seed
number is always the same… clock() has a way lower resolution so it
changes more often and not unimportant: If many users start the update
at the same time it isn't to unlikely the SRV record will be ordered in
the same second choosing the same for them all, but it seems less likely
that the exact same clock() time has passed for them.
And if I have to touch this, lets change a few other things as well to
make me and/or compilers a bit happier (clang complained about the usage
of a GNU extension in the testcase for example).
Add basic (non weight adjusted) shuffling for SrvRecords selection2015-08-20T09:41:51ZMichael Vogtmvo@debian.org2015-08-20T08:40:45Zurn:sha1:c29dbdffcb6f67812f823f1f844b87320cf6b437
Also add "Debug::Acquire::SrvRecs" debug option and the option
"Acquire::EnableSrvRecods" to allow disabling this lookup.