|
Size: 1579
Comment: more details about ticket dependencies
|
Size: 2918
Comment: spring cleanup
|
| 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 try to determine which attachments for a given Trac ticket to apply. To tell Patch Buildbot explicitly which patches to apply, write 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 patches 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}} '''New''' {{http://patchbot.sagemath.org/blob/Pending}}* '''Pending''' A patchbot is currently running on this ticket. {{http://patchbot.sagemath.org/blob/TestsPassed}} '''!TestsPassed''' Everything is okay, as far as a patchbot can tell. {{http://patchbot.sagemath.org/blob/ApplyFailed}} '''!ApplyFailed''' The branch could not be applied. This can be caused by conflicts with other patches or dependencies. {{http://patchbot.sagemath.org/blob/BuildFailed}} '''!BuildFailed''' The branch can be applied, but sage failed to build, due to errors in the doc or the code. {{http://patchbot.sagemath.org/blob/TestsFailed}} '''!TestsFailed''' One or more tests did not succeed. {{http://patchbot.sagemath.org/blob/PluginFailed}} '''!PluginFailed''' Plugins have found some problems. Tests have been successfully done. {{http://patchbot.sagemath.org/blob/PluginOnlyFailed}} '''!PluginOnlyFailed''' Plugin have found some problems. Tests have not been made. {{http://patchbot.sagemath.org/blob/PluginOnly}} '''!PluginOnly''' Plugins have found no problem. Tests have not been made. {{http://patchbot.sagemath.org/blob/NoPatch}} '''!NoPatch''' No patch has been uploaded to Trac so far. The patchbot has nothing to do. {{http://patchbot.sagemath.org/blob/Spkg}} '''Spkg''' This is not related to a patch but to a spkg. The patchbot is not concerned. |
| Line 26: | Line 51: |
| 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 patches 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:
New
* Pending A patchbot is currently running on this ticket.
TestsPassed Everything is okay, as far as a patchbot can tell.
ApplyFailed The branch could not be applied. This can be caused by conflicts with other patches or dependencies.
BuildFailed The branch can be applied, but sage failed to build, due to errors in the doc or the code.
TestsFailed One or more tests did not succeed.
PluginFailed Plugins have found some problems. Tests have been successfully done.
PluginOnlyFailed Plugin have found some problems. Tests have not been made.
PluginOnly Plugins have found no problem. Tests have not been made.
NoPatch No patch has been uploaded to Trac so far. The patchbot has nothing to do.
Spkg This is not related to a patch but to a spkg. The patchbot is not concerned.
Hints and tricks
To rerun tests (even though the branch was not modified) add the kick parameter, e.g., http://patchbot.sagemath.org/ticket/12345/?kick