Age | Commit message (Collapse) | Author | |
---|---|---|---|
2015-09-14 | srv test: do 100 pulls twice and compare list | David Kalnischkies | |
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 | |||
2015-09-01 | use clock() as source for SRV randomness | David Kalnischkies | |
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). | |||
2015-08-20 | Add basic (non weight adjusted) shuffling for SrvRecords selection | Michael Vogt | |
Also add "Debug::Acquire::SrvRecs" debug option and the option "Acquire::EnableSrvRecods" to allow disabling this lookup. | |||
2015-08-18 | cleanup | Michael Vogt | |
2014-05-23 | WIP start randomizing | Michael Vogt | |
2014-05-22 | WIP make connect use GetSrvRecords | Michael Vogt | |
2014-05-20 | add sorting by priority | Michael Vogt | |
2014-05-20 | add GetSrvRecord helper to apt-pkg/contrib/srvrec.{cc,h} | Michael Vogt | |