On Wed, Aug 18, 2010 at 11:29:14AM +0100, Eric Kow wrote: > On Tue, Aug 17, 2010 at 09:52:25 -0400, Nathan Gray wrote: > > On Mon, Aug 16, 2010, Eric Kow wrote: > > > Perhaps tar-bzip2 your ~/.darcs-benchmark directory and send it > > > our way. It could provide some clues, although I'm a bit doubtful > > > > Attached. > > Hmm, I notice that you have some darcs-2 format timings for the > "cap - darcs-2 format" repository in the 2010-08-13 timings file.
Yes. It started working correctly for my weekend run. Then
after my computer was unresponsive I have been unable to get
darcs-benchmark to run on any of the repos I had put in the list
of repos to test.
> > I tried several. I think the problem is that I tried to do a
> > bunch of them all together over the weekend. When that froze, or
> > died, or whatever it did when I was not watching, I am now not
> > able to run benchmarks on any of those repos.
> >
> > $ darcs-benchmark run darcs-2.4.98.3 / cap-hashed
> > No benchmarks to run for cap - hashed format
>
> Do you have configuration files for those repositories as well?
Attached.
> Also, I wonder if the filtering mechanism for repository variants
> is related to this. This is what it currently looks like (sorry for the
> Haskell):
>
> -- | The subset of variants appropriate to the given darcs version
> appropriateVariants :: TestBinary -> [Variant] -> [Variant]
> appropriateVariants bin = filter (appropriate . vId)
> where appropriate GitVariant
> | vcs /= VCSGit = False
> appropriate HgVariant
> | vcs /= VCSHg = False
> appropriate OptimizePristineVariant
> | vcs /= VCSDarcs || ver < [2,3,97] = False
> appropriate DefaultVariant
> | vcs /= VCSDarcs || ver > [2,4,96] = False
> appropriate _ = True
> vcs = binVCS bin
> ver = binVersion bin
Perhaps, but it does not seem likely since benchmarking started
working correctly for my first attempt. It has just not worked
after I let it churn over the weekend.
It does look like this command works:
$ darcs-benchmark run darcs-2.3.99.2 / cap-2-opt
Actually, looking at the timings file from the weekend, that is
the darcs binary it was testing. So perhaps this does have to do
with 'optimize pristine'.
I will try that and report back.
> > That seems to have worked. Running on my cap repos still results
> > in the same error.
>
> does darcs-benchmark report say anything about cap?
They are all identical, except for the name of the repo.
-kolibrie
$ darcs-benchmark run darcs-2.4.98.3 / cap-2-opt
No benchmarks to run for cap - darcs-2 optimized format
Benchmark Results
=====================================================
Machine description
*Replace Me*
Year
*Replace Me*
CPU
*Replace Me*
Memory
*Replace Me*
Hard disk
*Replace Me*
Notes
*Replace Me*
How to read these tables
=====================================================
NB: times are reported as mean + 1 std deviation
* ?x = less than 5 runs used
* ~x = less than 20 runs used
* sdev = std deviation
* op = optimize --pristine variant
Timing Graphs
====================================================
Timings
====================================================
Memory Graphs
====================================================
Memory
====================================================
{ "name" : "cap - darcs-2 optimized format"
, "path" : "repo.cap-2-opt"
, "annotate" : "README"
}
signature.asc
Description: Digital signature
_______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
