One thing I just noticed after applying one of Petr's test patches. If
you don't have a global cache directory (as in the case in the
regression tests), darcs will complain about not being able to reach it.
This sounds like it may be an easy exception to account for. Could you
investigate and see what needs to be done? I think you only need to
handle the case of the default global cache dir.
This is actually a major regression, since I am seeing this, if the
global cache does not exist (running cabal test get-http -- you need
lighttpd for that, and you need to run *only* that -- an earlier test
would have created the global cache...).
+ darcs get http://localhost:23032/R S
Hash failure in
darcs failed: Couldn't fetch
in subdir pristine.hashed from sources:
For all I can tell, this is because the code tries to check cache
reachability *before* trying to create it, which consequently leads it
to to forget to write the actual file it intended to write.
Well, seems like an easy fix, submitting now... please review ASAP.
The following patch updated issue issue1908 with status=resolved;resolvedin=2.8.0 HEAD
* Resolve issue1908: try to create a global cache before checking its availability.
Rebased to resolve conflict & removed Setup.hs
1 patch for repository http://darcs.net/screened:
Author: Ben Franksen <email@example.com>
Date: Sat Jan 25 13:09:59 CET 2020
* WIP: drop custom Setup.hs