Is there a buildbot I can check my results against? At
http://buildbot.djangoproject.com/
the bots only say which Django, Python and database is being tested, but
not on which platform, but they all seem to be Linux/Unix so I am
guessing they all run on the same machine.
regards
Steve
--
Steve Holden +1 571 484 6266 +1 800 494 3119
Holden Web LLC http://www.holdenweb.com/
If you're getting errors please submit tickets into Trac.
> If you're getting errors please submit tickets into Trac.
>
Right ho.
regards
Steve
I had started the http://code.djangoproject.com/wiki/DjangoOnWindows
wikipage to (among otehr things) track the failures seen under Windows
with pointers to the respective tickets and comments about the issues.
But I haven't run the test suite during the last week or so, so taking in
account the activenness of trunk in suuch period and what you say, that
page is most surely out of date.
I wil try to update it with pointers to the tickets you open if you decide
to do so. or will open these tickets myself.
Regards,
--
Ramiro Morales
How actively is the Windows community testing Django? With the second
beta due out soon (though not as soon as originally anticipated) I
thought I'd try it out yesterday, and I see that with the recent signal
patch applied I get 1 failure. My trunk checkout gave 2 failures with 12
errors.
Is there a buildbot I can check my results against? At
http://buildbot.djangoproject.com/
the bots only say which Django, Python and database is being tested, but
not on which platform, but they all seem to be Linux/Unix so I am
guessing they all run on the same machine.
>
> I've been trying to test on Windows fairly regularly (though I consider
> myself more a member of the Django community who happens to have Windows
> boxes for test, rather than a member of the Windows community). For some
> time I have observed this failure:
>
> http://code.djangoproject.com/ticket/7570
>
> When streaming file uploads went in there were a couple others that cropped
> up but by the time I saw them there were already tickets open for them and
> they have now all been resolved. Running the test suite on Windows this
> morning with r8222 I again see only that one failure documented above (plus
> a note that GDAL is not available therefore those tests aren't being
> run...first time I've noticed that,
I was going to post reporting that I ran the suite with an up to date
checkout and found only the same (known) failure.
Steve: Wwhat DB backend are running the suite against?. Also,
I'd suggest to doble check if the SVN WC isn't borked somehow
(for example making sure to delete the regressiontests\maxlength
directory that could introduce some bogus failures.)
Regards,
--
Ramiro Morales
Update: As of r8223 (i.e. post GeoDjango and signal refactoring merging)
there are no new failures on this platform.
--
Ramiro Morales
Before I log any tickets I'll start with a clean checkout.