Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
Without this fix "make check" will fail if called outside of the source
directory.
|
|
|
|
|
|
files.
This has no impact on the cache replacement policy: the CacheId field
is still used to implement an LRU policy. This information will be
useful for items that are fetched from the network: we can use it to
avoid fetching a second copy of a file when the current data is already
up-to-date, without just not checking for updates (and hence possibly
storing an out-of-date version of the file forever).
This will be used for screenshot support, since unlike changelogs,
screenshots might change. (it could be used for changelogs too, but
since the changelog of a given version never changes, it's probably
overkill for the time being -- maybe once we can read non-Debian
changelogs this will make sense)
|
|
This unfortunately doesn't test that memory is actually used; I'm not
sure how to test that. Anyway, it's not guaranteed that all the items
will be available unless the file cache is large enough to hold them
all -- it coincidentally worked in previous builds, but won't work with
compressed cache entries, which behave differently due to having
different sizes for the items that are stored.
|
|
* The order in which entries were touched was wrong (I was touching
the entry that should have been least-recently-used last ... oops).
* Need to generate a new temporary file for each sub-test; otherwise
we end up re-opening the same cache that was used for the last test,
leading to trouble when we try to reset the test.
|
|
|
|
|
|
|
|
cache test is meaningless if it doesn't work).
|
|
|
|
|
|
The plan is to use BLOB storage in sqlite. This is less than entirely
efficient, but it should avoid having a lot of small files hanging
around and having to manage the cache contents myself. Hopefully the
load on the cache will be low enough that the BLOBs are reasonable.
I've split them into a separate table in the hope that it'll help.
The only thing not implemented at the moment is actually putting files
in and getting them out, i.e. the most important part. The tests are
only just started, too.
|