On Tue, Jul 8, 2008 at 12:56 PM, [EMAIL PROTECTED] wrote:
It looks to me like the main thing that Pybots needs is help with
maintenance. Getting someone to set up an individual buildbot is one thing,
but keeping it working is the important bit and it looks like people are not
doing that.
On Mon, Jul 7, 2008 at 5:39 AM, Antoine Pitrou [EMAIL PROTECTED] wrote:
- are more buildbots needed and if so, which kinds of platforms/architectures?
I can't really answer that question for the python code buildbot farm,
but for the Pybots community project, the platforms we currently have
On Sun, Jul 6, 2008 at 2:09 PM, Grig Gheorghiu [EMAIL PROTECTED] wrote:
I'll send a message to the pybots mailing list asking people whose
buildbots are turned off if they're still interested in running them.
Negative or no answers will mean we can remove them from the farm.
OK, I posted
On Sun, Jul 6, 2008 at 8:46 AM, [EMAIL PROTECTED] wrote:
However, let's say that this were tremendously successful, and lots of
people start paying attention. I think pybots.org needs to be updated to
say exactly what a participant interested in python testing needs to do,
beyond here's how
On Thu, Jun 26, 2008 at 8:18 AM, [EMAIL PROTECTED] wrote:
Today on planetpython.org, Doug Hellman announced the June issue of Python
magazine. The cover story this month is about Pybots, the fantastic
automation system that has been put in place to make sure new releases of
Python software
When I go to
http://www.python.org/dev/buildbot/community/all/
I get a 503 error Service Temporarily Unavailable.
Can anybody shed some light?
Thanks,
Grig
--
http://agiletesting.blogspot.com
___
Python-Dev mailing list
Python-Dev@python.org
This is happening both in the Python buildbot farm, and in the
community buildbot farm.
See:
http://www.python.org/dev/buildbot/trunk/sparc%20solaris10%20gcc%20trunk/builds/1960/step-test/0
http://www.python.org/dev/buildbot/community/trunk/sparc%20Solaris%2010%20trunk/builds/484/step-test/0
Almost all community buildbots have failed the test step due to a
failure in test_normalization. Here's a link to the community farm for
the trunk:
http://www.python.org/dev/buildbot/community/trunk/
And here's an example of a failure:
On 4/16/07, Brett Cannon [EMAIL PROTECTED] wrote:
Don't know what suddenly triggered this (nothing I did), but the code
basically looks correct. What should be happening is regrtest should be
catching that exception and just saying the test was skipped.
The last commit on regrtest was March
On 3/8/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Buildbot has a build this branch feature which could be used to settle
these discussions more rapidly, except for the fact that the community
builders are currently in pretty sad shape:
Sidnei da Silva asked on the pybots mailing list if we should be
testing packages with py3k. I think it's probably too early for that,
but on the other hand I'm sure many package creators/maintainers would
be curious to see how their packages fare with py3k.
So is there any value or interest in
On 11/7/06, Martin v. Löwis [EMAIL PROTECTED] wrote:
Grig Gheorghiu schrieb:
One of the Pybots buildslaves running x86 Ubuntu Edgy has been failing
the unit test step for the trunk, specifically the test_ucn test.
Something is wrong with the machine. I forced a clean rebuild, and
now
One of the Pybots buildslaves running x86 Ubuntu Edgy has been failing
the unit test step for the trunk, specifically the test_ucn test.
Here's the error:
test_ucn
test test_ucn failed -- Traceback (most recent call last):
File /home/pybot/pybot/trunk.bear-x86/build/Lib/test/test_ucn.py,
line
On 10/19/06, Martin v. Löwis [EMAIL PROTECTED] wrote:
Grig Gheorghiu schrieb:
OK, I deleted the checkout directory on one of my buidslaves and
re-ran the build steps. The tests passed. So my conclusion is that a
full rebuild is needed for the tests to pass after the last checkins
(which
On 10/20/06, Martin v. Löwis [EMAIL PROTECTED] wrote:
Grig Gheorghiu schrieb:
Maybe the makefiles should be modified so that a full rebuild is
triggered when the configure and configure.in files are changed?
The makefiles already do that: if configure changes, a plain
make will first
The latest trunk checkin caused almost all Pybots to fail when running
the Python unit tests.
273 tests OK.
12 tests failed:
test___all__ test_calendar test_capi test_datetime test_email
test_email_renamed test_imaplib test_mailbox test_strftime
test_strptime test_time test_xmlrpc
On 10/19/06, Brett Cannon [EMAIL PROTECTED] wrote:
Possibly. If you look at the reason those tests failed it is because
time.strftime is missing for some odd reason. But none of recent checkins
seem to have anything to do with the 'time' module, let alone with how
methods are added to
On 10/19/06, Brett Cannon [EMAIL PROTECTED] wrote:
On 10/19/06, Grig Gheorghiu [EMAIL PROTECTED] wrote:
On 10/19/06, Brett Cannon [EMAIL PROTECTED] wrote:
Possibly. If you look at the reason those tests failed it is because
time.strftime is missing for some odd reason. But none
FYI -- can't do svn checkouts/updates from the trunk at this point.
starting svn operation
svn update --revision HEAD
in dir /home/twistbot/pybot/trunk.gheorghiu-x86/build (timeout 1200 secs)
svn: PROPFIND request failed on '/projects/python/trunk'
svn: PROPFIND of '/projects/python/trunk':
On 10/17/06, Kristján V. Jónsson [EMAIL PROTECTED] wrote:
Okay, a buildbot then doesn't sound quite that scary. Any info somewhere on
how to set one up on a windows box?
http://wiki.python.org/moin/BuildbotOnWindows
Grig
___
Python-Dev mailing
On 10/17/06, Anthony Baxter [EMAIL PROTECTED] wrote:
On Wednesday 18 October 2006 00:59, Grig Gheorghiu wrote:
FYI -- can't do svn checkouts/updates from the trunk at this point.
starting svn operation
svn update --revision HEAD
in dir /home/twistbot/pybot/trunk.gheorghiu-x86/build
On 9/21/06, Jack Diederich [EMAIL PROTECTED] wrote:
The python binary is out of step with the test_itertools.py version.
You can generate this same error on your own box by reverting the
change to itertoolsmodule.c but leaving the new test in test_itertools.py
I don't know why this only
On 9/21/06, Jack Diederich [EMAIL PROTECTED] wrote:
On Thu, Sep 21, 2006 at 03:28:04PM -0700, Grig Gheorghiu wrote:
On 9/21/06, Jack Diederich [EMAIL PROTECTED] wrote:
The python binary is out of step with the test_itertools.py version.
You can generate this same error on your own box
On 9/21/06, Grig Gheorghiu [EMAIL PROTECTED] wrote:
On 9/21/06, Jack Diederich [EMAIL PROTECTED] wrote:
On Thu, Sep 21, 2006 at 03:28:04PM -0700, Grig Gheorghiu wrote:
On 9/21/06, Jack Diederich [EMAIL PROTECTED] wrote:
The python binary is out of step with the test_itertools.py version
When the pybot buildslave for Twisted is trying to run the Twisted test suite via 'trial', it gets an exception:Traceback (most recent call last): File /tmp/Twisted/bin/trial, line 23, in module
from twisted.scripts.trial import run File /tmp/Twisted/twisted/scripts/trial.py, line 10, in
On 8/31/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
There was a buildbot set up recently to test various external packages(like twisted) against Python's source code.I don't recall where it is,but it would be nice if relevant links to it existed on this page:
On 7/28/06, Neal Norwitz [EMAIL PROTECTED] wrote:
On 7/27/06, A.M. Kuchling [EMAIL PROTECTED] wrote: On Thu, Jul 27, 2006 at 05:40:57PM +0200, Georg Brandl wrote: The UUID test suite, which wasn't run by regrtest.py until now, is
now failing on some buildbots (and my machine). This should be
Hi,
This message is in response to Glyph's plea
(http://mail.python.org/pipermail/python-dev/2006-July/067366.html).
Here's what Glyph said:
I would like to propose, although I certainly don't have time to
implement, a program by which Python-using projects could contribute
buildslaves which
On 7/25/06, Neal Norwitz [EMAIL PROTECTED] wrote:
If you want I can send you the build master cfg I setup on python.organd some simple instructions for how to connect to it.I don't havetime to focus on this at the moment and probably won't until
2.5 isout.n--Sure. I'm still a bit unclear on
On 7/22/06, Martin v. Löwis [EMAIL PROTECTED] wrote:
Grig Gheorghiu wrote: Please let me know if you're interested.As I said earlier: If you need some kind of post-committrigger on the python repository to trigger a build, justlet me know. We currently use a more-or-less plain
svn_buildbot.py
On 7/22/06, Martin v. Löwis [EMAIL PROTECTED] wrote:
Grig Gheorghiu wrote: As I said earlier: If you need some kind of post-commit trigger on the python repository to trigger a build, just let me know. We currently use a more-or-less plain
svn_buildbot.py to trigger our own builds. Wouldn't
Hi,This message is in response to Glyph's plea(http://mail.python.org/pipermail/python-dev/2006-July/067366.html
).Here's what Glyph said:I would like to propose, although I certainly don't have time toimplement, a program by which Python-using projects could contributebuildslaves which would run
32 matches
Mail list logo
