Differences between revisions 5 and 28 (spanning 23 versions)
Revision 5 as of 2011-01-28 07:26:54
Size: 1704
Editor: robertwb
Comment:
Revision 28 as of 2015-09-16 09:43:22
Size: 3714
Editor: chapoton
Comment:
Deletions are marked like this. Additions are marked like this.
Line 5: Line 5:
The first builds entire tarballs (e.g. all the alphas) on a wide variety of machines, and can be found at http://build.sagemath.org/sage/ . The first builds entire tarballs (e.g. all the development releases) on a wide variety of machines. It can be found at http://build.sagemath.org/sage/ .
Line 7: Line 7:
== Patch Buildbot == == Patch Buildbot (Patchbot) ==
Line 9: Line 9:
The second pulls and applies patches from trac and can be found at http://sage.math.washington.edu:21100/ticket/ or from links on the individual trac tickets. This is still very much a work in progress, but the latest version of the code lives at http://sage.math.washington.edu/home/robertwb/buildbot/bot/ . Eventually this will get moved into Sage where it can be edited using the standard procedures and more widely deployed. The second pulls and applies git branches from Trac and can be found at http://patchbot.sagemath.org/ or from links on the individual Trac tickets (round icons at top right).
Line 11: Line 11:
=== Usage === You can help by running your own patchbot. See this [[buildbot/details|instruction page]] for installation and usage.
Line 13: Line 13:
Patch Buildbot will usually be able to to determine which attachments for a given Trac ticket to apply; when in doubt click on the swirly blob to see it's plan of action. If it is unable to figure out what to do, tell Patch Buildbot explicitly which patches to apply by writing something like the following in any comment: This is still very much a work in progress; the latest version of the code lives at http://github.com/robertwb/sage-patchbot. Eventually this will get moved into Sage where it can be edited using the standard procedures and more widely deployed. See ticket http://trac.sagemath.org/sage_trac/ticket/12486.
Line 15: Line 15:
    Apply foo.patch, foo2.patch === Lists of reports ===
Line 17: Line 17:
This will "reset" the patch list at that point. Any subsequently added patches will
get (semi-intellegently) appended to the list. The list of attachments which will be applied on the next run are listed at the top of the buildbot report page for that ticket (the page you get by clicking on the swirly round icon at the top of the ticket description).
You can see the status of several tickets at the same time (replace xxxx by your user name) :
Line 20: Line 19:
To tell Patch Buildbot about any ticket dependencies, write something like the following in any comment: For the tickets you participated in, see http://patchbot.sagemath.org/ticket/?participant=xxxx
Line 22: Line 21:
    Depends on #1719 For the tickets you authored, see http://patchbot.sagemath.org/ticket/?author=xxxx

=== Ticket Status ===

The color of the report page icon indicates the status of the ticket. See the report page itself for more details. The possible statuses are:

{{http://patchbot.sagemath.org/blob/New}} {{http://patchbot.sagemath.org/svg/New||width=48}} '''New'''

{{http://patchbot.sagemath.org/blob/Pending}}* {{http://patchbot.sagemath.org/svg/Pending||width=48}} '''Pending''' A patchbot is currently running on this ticket. The patchbot may have stopped if the ticket was deemed unsafe.

{{http://patchbot.sagemath.org/blob/TestsPassed}} {{http://patchbot.sagemath.org/svg/TestsPassed||width=48}} '''!TestsPassed''' Everything is okay, as far as a patchbot can tell.

{{http://patchbot.sagemath.org/blob/ApplyFailed}} {{http://patchbot.sagemath.org/svg/ApplyFailed||width=48}} '''!ApplyFailed''' The branch could not be applied. This can be caused by conflicts with other branches or dependencies. Try rebase your branch on the latest develop branch.

{{http://patchbot.sagemath.org/blob/BuildFailed}} {{http://patchbot.sagemath.org/svg/BuildFailed||width=48}} '''!BuildFailed''' The branch can be applied, but sage failed to build, due to errors in the doc or the code. Check the code and the syntax of the doc.

{{http://patchbot.sagemath.org/blob/TestsFailed}} {{http://patchbot.sagemath.org/svg/TestsFailed||width=48}} '''!TestsFailed''' One or more tests did not succeed.

{{http://patchbot.sagemath.org/blob/PluginFailed}} {{http://patchbot.sagemath.org/svg/PluginFailed||width=48}} '''!PluginFailed''' Tests have been successfully done, but plugins have found some problems.
{{http://patchbot.sagemath.org/blob/PluginOnlyFailed}} {{http://patchbot.sagemath.org/svg/PluginOnlyFailed||width=48}} '''!PluginOnlyFailed''' Plugin have found some problems. Tests have not been made.

{{http://patchbot.sagemath.org/blob/PluginOnly}} {{http://patchbot.sagemath.org/svg/PluginOnly||width=48}} '''!PluginOnly''' Plugins have found no problem. Tests have not been made.

{{http://patchbot.sagemath.org/blob/NoPatch}} {{http://patchbot.sagemath.org/svg/NoPatch||width=48}} '''!NoPatch''' No branch has been uploaded to Trac so far. The patchbot has nothing to do.

{{http://patchbot.sagemath.org/blob/Spkg}} {{http://patchbot.sagemath.org/svg/Spkg||width=48}} '''Spkg''' This is related to an spkg. The patchbot will only check the spkg installation.
Line 26: Line 50:
Detecting ticket dependencies and which patches to apply are both performed by string searches on each line of the ticket, and are case insensitive.  * To rerun tests (even though the branch was not modified) add the kick parameter, e.g., http://patchbot.sagemath.org/ticket/12345/?kick

Sage has two build bots.

Release Buildbot

The first builds entire tarballs (e.g. all the development releases) on a wide variety of machines. It can be found at http://build.sagemath.org/sage/ .

Patch Buildbot (Patchbot)

The second pulls and applies git branches from Trac and can be found at http://patchbot.sagemath.org/ or from links on the individual Trac tickets (round icons at top right).

You can help by running your own patchbot. See this instruction page for installation and usage.

This is still very much a work in progress; the latest version of the code lives at http://github.com/robertwb/sage-patchbot. Eventually this will get moved into Sage where it can be edited using the standard procedures and more widely deployed. See ticket http://trac.sagemath.org/sage_trac/ticket/12486.

Lists of reports

You can see the status of several tickets at the same time (replace xxxx by your user name) :

For the tickets you participated in, see http://patchbot.sagemath.org/ticket/?participant=xxxx

For the tickets you authored, see http://patchbot.sagemath.org/ticket/?author=xxxx

Ticket Status

The color of the report page icon indicates the status of the ticket. See the report page itself for more details. The possible statuses are:

http://patchbot.sagemath.org/blob/New http://patchbot.sagemath.org/svg/New New

http://patchbot.sagemath.org/blob/Pending* http://patchbot.sagemath.org/svg/Pending Pending A patchbot is currently running on this ticket. The patchbot may have stopped if the ticket was deemed unsafe.

http://patchbot.sagemath.org/blob/TestsPassed http://patchbot.sagemath.org/svg/TestsPassed TestsPassed Everything is okay, as far as a patchbot can tell.

http://patchbot.sagemath.org/blob/ApplyFailed http://patchbot.sagemath.org/svg/ApplyFailed ApplyFailed The branch could not be applied. This can be caused by conflicts with other branches or dependencies. Try rebase your branch on the latest develop branch.

http://patchbot.sagemath.org/blob/BuildFailed http://patchbot.sagemath.org/svg/BuildFailed BuildFailed The branch can be applied, but sage failed to build, due to errors in the doc or the code. Check the code and the syntax of the doc.

http://patchbot.sagemath.org/blob/TestsFailed http://patchbot.sagemath.org/svg/TestsFailed TestsFailed One or more tests did not succeed.

http://patchbot.sagemath.org/blob/PluginFailed http://patchbot.sagemath.org/svg/PluginFailed PluginFailed Tests have been successfully done, but plugins have found some problems. http://patchbot.sagemath.org/blob/PluginOnlyFailed http://patchbot.sagemath.org/svg/PluginOnlyFailed PluginOnlyFailed Plugin have found some problems. Tests have not been made.

http://patchbot.sagemath.org/blob/PluginOnly http://patchbot.sagemath.org/svg/PluginOnly PluginOnly Plugins have found no problem. Tests have not been made.

http://patchbot.sagemath.org/blob/NoPatch http://patchbot.sagemath.org/svg/NoPatch NoPatch No branch has been uploaded to Trac so far. The patchbot has nothing to do.

http://patchbot.sagemath.org/blob/Spkg http://patchbot.sagemath.org/svg/Spkg Spkg This is related to an spkg. The patchbot will only check the spkg installation.

Hints and tricks