Hi,
I'm testing my faulthandler repository on the custom buildbots, here are some remarks and issues.
The form still refers to SVN ('Branch to build' is relative to http://svn.python.org/projects/python.) => the branch is relative to hg.python.org/
I cannot write "#" in the branch field to specify... the branch (only the repository). If the branch contains "#", the request looks to be ignored (without any warning/error). I merged my faulthandler branch into the default branch (in my features/faulthandler branch).
I don't understand the meaning of the "project" field. It is maybe something specific to Subversion?
What are the 3 optional properties?
If branch doesn't end with a slash (e.g. "features/faulthandler"), the request is ignored (without any warning/error).
I canceled a build on a Windows buildbot during the "tests" step using the [Cancel] button, but it failed to kill the process:
http://www.python.org/dev/buildbot/all/builders/x86%20Windows7% 20custom/builds/2/steps/test/logs/stdio ----------- command interrupted, killing pid 2168 SIGKILL failed to kill process using fake rc=-1 program finished with exit code -1 -----------
To test my faulthandler feature branch, the correct parameters are: -- Name: haypo Reason: test faulthandler Branch: features/faulthandler/ Revision: tip Repository: features/faulthandler (leave the project and the 6 property fields empty) --
The repository looks like a duplicate of the branch field. I would be better to use "default" as the branch and "features/faulthandler" as the repository.
I would be nice to have error messages.
Victor
On Wed, 30 Mar 2011 17:59:02 +0200 Victor Stinner victor.stinner@haypocalc.com wrote:
I cannot write "#" in the branch field to specify... the branch (only the repository). If the branch contains "#", the request looks to be ignored (without any warning/error). I merged my faulthandler branch into the default branch (in my features/faulthandler branch).
You could have put the branch name in the "revision" field instead (as I told you on #python-dev).
This is very much an unofficial feature right now, which also explains that the UI has not been adapted.
I canceled a build on a Windows buildbot during the "tests" step using the [Cancel] button, but it failed to kill the process:
http://www.python.org/dev/buildbot/all/builders/x86%20Windows7% 20custom/builds/2/steps/test/logs/stdio
command interrupted, killing pid 2168 SIGKILL failed to kill process using fake rc=-1 program finished with exit code -1
This is the kind of question you have to ask on the buildbot channels. I don't think any of us knows enough about buildbot internals to answer it or give any guidance.
Thank you
Antoine.
Le mercredi 30 mars 2011 à 17:59 +0200, Victor Stinner a écrit :
I'm testing my faulthandler repository on the custom buildbots, here are some remarks and issues.
Oh, I forgot something: there is an error on hg purge.
Example on a Windows buildbot: ---- C:\Program Files\Mercurial\hg.EXE purge --all ... argv: ['C:\\Program Files\\Mercurial\\hg.EXE', 'purge', '--all'] ... program finished with exit code -1 'hg purge' failed: Mercurial Distributed SCM ----
It looks like build slaves require the purge extension.
Victor
On Wed, 30 Mar 2011 18:11:53 +0200 Victor Stinner victor.stinner@haypocalc.com wrote:
Le mercredi 30 mars 2011 à 17:59 +0200, Victor Stinner a écrit :
I'm testing my faulthandler repository on the custom buildbots, here are some remarks and issues.
Oh, I forgot something: there is an error on hg purge.
[...]
It's not an error, it falls back on another purging method when the purge extension is not enabled.
cheers
Antoine.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 30/03/11 18:27, Antoine Pitrou wrote:
On Wed, 30 Mar 2011 18:11:53 +0200 Victor Stinner victor.stinner@haypocalc.com wrote:
Le mercredi 30 mars 2011 à 17:59 +0200, Victor Stinner a écrit :
I'm testing my faulthandler repository on the custom buildbots, here are some remarks and issues.
Oh, I forgot something: there is an error on hg purge.
[...]
It's not an error, it falls back on another purging method when the purge extension is not enabled.
I guess you are talking about http://mercurial.selenic.com/wiki/PurgeExtension. Do you want me to activate this extension in my buildbots? (OpenIndiana machine).
- -- Jesus Cea Avion _/_/ _/_/_/ _/_/_/ jcea@jcea.es - http://www.jcea.es/ _/_/ _/_/ _/_/ _/_/ _/_/ jabber / xmpp:jcea@jabber.org _/_/ _/_/ _/_/_/_/_/ . _/_/ _/_/ _/_/ _/_/ _/_/ "Things are not so easy" _/_/ _/_/ _/_/ _/_/ _/_/ _/_/ "My name is Dump, Core Dump" _/_/_/ _/_/_/ _/_/ _/_/ "El amor es poner tu felicidad en la felicidad de otro" - Leibniz
For the record, I added a page documenting our continuous integration setup at: http://docs.python.org/devguide/buildbots.html
Regards
Antoine.
On Wed, 30 Mar 2011 17:59:02 +0200 Victor Stinner victor.stinner@haypocalc.com wrote:
Hi,
I'm testing my faulthandler repository on the custom buildbots, here are some remarks and issues.
The form still refers to SVN ('Branch to build' is relative to http://svn.python.org/projects/python.) => the branch is relative to hg.python.org/
I cannot write "#" in the branch field to specify... the branch (only the repository). If the branch contains "#", the request looks to be ignored (without any warning/error). I merged my faulthandler branch into the default branch (in my features/faulthandler branch).
I don't understand the meaning of the "project" field. It is maybe something specific to Subversion?
What are the 3 optional properties?
If branch doesn't end with a slash (e.g. "features/faulthandler"), the request is ignored (without any warning/error).
I canceled a build on a Windows buildbot during the "tests" step using the [Cancel] button, but it failed to kill the process:
http://www.python.org/dev/buildbot/all/builders/x86%20Windows7% 20custom/builds/2/steps/test/logs/stdio
command interrupted, killing pid 2168 SIGKILL failed to kill process using fake rc=-1 program finished with exit code -1
To test my faulthandler feature branch, the correct parameters are:
Name: haypo Reason: test faulthandler Branch: features/faulthandler/ Revision: tip Repository: features/faulthandler (leave the project and the 6 property fields empty) --
The repository looks like a duplicate of the branch field. I would be better to use "default" as the branch and "features/faulthandler" as the repository.
I would be nice to have error messages.
Victor
On Wed, Mar 30, 2011 at 5:01 PM, Antoine Pitrou solipsis@pitrou.net wrote:
For the record, I added a page documenting our continuous integration setup at: http://docs.python.org/devguide/buildbots.html
Regards
Antoine.
that's awesome. should we document how to donate/add a buildbot somewhere in the same section (or alongside)?
On Wed, 30 Mar 2011 17:14:10 -0400 Jesse Noller jnoller@gmail.com wrote:
On Wed, Mar 30, 2011 at 5:01 PM, Antoine Pitrou solipsis@pitrou.net wrote:
For the record, I added a page documenting our continuous integration setup at: http://docs.python.org/devguide/buildbots.html
Regards
Antoine.
that's awesome. should we document how to donate/add a buildbot somewhere in the same section (or alongside)?
It's documented at http://wiki.python.org/moin/BuildBot. I think it's a bit outside the scope of the devguide.
(perhaps we should have an infrastructure/sysadmin contribution guide)
Regards
Antoine.
On Wed, Mar 30, 2011 at 5:24 PM, Antoine Pitrou solipsis@pitrou.net wrote:
On Wed, 30 Mar 2011 17:14:10 -0400 Jesse Noller jnoller@gmail.com wrote:
On Wed, Mar 30, 2011 at 5:01 PM, Antoine Pitrou solipsis@pitrou.net wrote:
For the record, I added a page documenting our continuous integration setup at: http://docs.python.org/devguide/buildbots.html
Regards
Antoine.
that's awesome. should we document how to donate/add a buildbot somewhere in the same section (or alongside)?
It's documented at http://wiki.python.org/moin/BuildBot. I think it's a bit outside the scope of the devguide.
(perhaps we should have an infrastructure/sysadmin contribution guide)
Not a bad idea.
>> For the record, I added a page documenting our continuous integration >> setup at: http://docs.python.org/devguide/buildbots.html
Jesse> that's awesome. should we document how to donate/add a buildbot Jesse> somewhere in the same section (or alongside)?
I must admit, it wasn't obvious to me where the link to this page exists in the devguide. Also, I see a link to this page:
http://python.org/dev/buildbot/
labelled "buildbot status". Should it link back to Antoine's new page?
S
participants (5)
-
Antoine Pitrou -
Jesse Noller -
Jesus Cea -
skip＠pobox.com -
Victor Stinner