On 12/16/06, D.J. Heap <email@example.com> wrote:
> > Questions About the Tests:
> > We're passing all 48 of the 48 tests run and we are skipping 30 tests. Does
> > this match others? Or can more of the tests be run with a better build?
> That sounds about right, although its a lot more than 48 tests -- each
> of those output lines is a set of tests. The skipped lines are
> individual tests that were skipped due to being irrelevant or not
> applicable to the platform (no executable bit or symlinks on Windows).
Thanks for the reassurance about the warnings and the number of tests.
I like the counting that happens when running the tests on the trunk
vs 1.4.2. Since the tests take about an hour and twenty minutes, I
assumed there was a lot going on there.
> > Since the build-bot doesn't seem to be doing windows at the moment, is there
> > somewhere else on the web I can check how others windows builds are going?
> What buildbot are you looking at? There is definitely one for Windows
> although it uses VC2005 Express and has been running http/ra_dav tests
> lately, rather than file/ra_local tests.
I was looking at http://www.mobsol.be/buildbot/ (I followed the link
from the hackers guide). I see now the VS2005 version, but I was
focused on VC6 since (I think) that is the version used to generate
the subversion binaries and it is the version used to build the
one-click installer of Ruby.
> > On to building the Perl and Python bindings!
> If you get Ruby to work please post back on what you did -- I don't
> know of anyone that has built them on Windows (I tried a while back
> but gave up rather quickly after getting lots of preprocessor errors
> in the generated swig files).
That has been my plan all along. With your assurances that I've
successfully built subversion, I'll be posting soon about what I'm
learning about the bindings. Unfortunately, my laptop ac adaptor died
so I'm stuck for a couple days until UPS comes through.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Sun Dec 17 06:42:37 2006