On 8 April 2014 20:11, Thomas Vandahl wrote:
> On 07.04.14 21:38, sebb wrote:
>>> Indeed. It also has some peculiar behaviour in that it allows the
>>> storage directory to be changed after initialisation.
>>> Looks like the directory can be anywhere so it might use a directory
>>> with existing f
On 07.04.14 21:38, sebb wrote:
>> Indeed. It also has some peculiar behaviour in that it allows the
>> storage directory to be changed after initialisation.
>> Looks like the directory can be anywhere so it might use a directory
>> with existing files in it that are not actually cache files.
>> See
On 7 April 2014 20:13, sebb wrote:
> On 7 April 2014 18:39, Thomas Vandahl wrote:
>> On 04.04.14 02:32, sebb wrote:
>>> The FileDiskCacheUnitTest was failing because the tests were dependent
>>> on the file timestamp resolution, so the cache did not always treat
>>> the first created file as the
On 7 April 2014 18:39, Thomas Vandahl wrote:
> On 04.04.14 02:32, sebb wrote:
>> The FileDiskCacheUnitTest was failing because the tests were dependent
>> on the file timestamp resolution, so the cache did not always treat
>> the first created file as the oldest.
>> Adding pauses as necessary fixe
On 04.04.14 02:32, sebb wrote:
> The FileDiskCacheUnitTest was failing because the tests were dependent
> on the file timestamp resolution, so the cache did not always treat
> the first created file as the oldest.
> Adding pauses as necessary fixed this.
I inherited the code. Personally, I'd throw
I'm gradually working my way through the test failures that occur on Continuum.
The FileDiskCacheUnitTest was failing because the tests were dependent
on the file timestamp resolution, so the cache did not always treat
the first created file as the oldest.
Adding pauses as necessary fixed this.
I
