|
Size: 2361
Comment:
|
Size: 3006
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://patchbot.sagemath.org/ 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 https://code.google.com/p/sage-buildbot/ . 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 https://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: |
| The Patch Buildbot will automatically select patches (from the ticket attachments) to apply. Every Trac ticket has a Patch Buildbot report page, which is accessed by the swirly, round icon at the top of the ticket description. The report page lists the patches the buildbot chose. To override this choice, use the following directive in a ticket comment: | This is still very much a work in progress. The latest version of the code lives at http://github.com/sagemath/sage-patchbot. |
| Line 15: | Line 15: |
| Apply foo.patch, foo2.patch | === Lists of reports === |
| Line 17: | Line 17: |
| Any subsequently added patches will be (semi-intellegently) appended to the list. To tell Patch Buildbot about any ticket dependencies, populate the dependencies field with the ticket numbers and/or minimum Sage version. | You can see the status of several tickets at the same time (replace xxxx by your user name) : |
| Line 19: | Line 19: |
| Only the devel repository has branches, so the buildbot is unable to apply and try out patches to extcode/scripts/etc. | For the tickets you participated in, see https://patchbot.sagemath.org/ticket/?base=develop&participant=xxxx |
| Line 21: | Line 21: |
| === Patch Status === | For the tickets you authored, see https://patchbot.sagemath.org/ticket/?base=develop&author=xxxx |
| Line 23: | Line 23: |
| Patches can have the following status: | === Ticket Status === |
| Line 25: | Line 25: |
| * New (grey) | 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: |
| Line 27: | Line 27: |
| * ApplyFailed (red) The patch could not be applied. This can be caused by conflicts with other patches or dependencies. | {{https://patchbot.sagemath.org/svg/New||width=48}} '''New''' |
| Line 29: | Line 29: |
| * BuildFailed (red) | {{https://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. |
| Line 31: | Line 31: |
| * TestsFailed (yellow) Some tests did not succeed. They can be found in the report of the bot. | {{https://patchbot.sagemath.org/svg/TestsPassed||width=48}} '''!TestsPassed''' Everything is okay, as far as a patchbot can tell. |
| Line 33: | Line 33: |
| * PluginFailed (blue) Documentation and commit messages should be checked, see the bot report. | {{https://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. |
| Line 35: | Line 35: |
| * TestsPassed (green) Everything is ok, as far as the bot can tell. | {{https://patchbot.sagemath.org/svg/BuildFailed||width=48}} '''!BuildFailed''' The branch can be applied, but sage failed to build, due to errors in the code. Check the code. |
| Line 37: | Line 37: |
| * Pending (grey) The bot is currently running on this patch. | {{https://patchbot.sagemath.org/svg/TestsFailed||width=48}} '''!TestsFailed''' One or more tests did not succeed. |
| Line 39: | Line 39: |
| * NoPatch (purple) No patch has been uploaded to trac so far. The bot has nothing to do. | {{https://patchbot.sagemath.org/svg/PluginFailed||width=48}} '''!PluginFailed''' Tests have been successfully done, but plugins have found some problems. |
| Line 41: | Line 41: |
| * Spkg (purple) This is not related to a patch but to a spkg package. The bot is not concerned. | {{https://patchbot.sagemath.org/svg/PluginOnlyFailed||width=48}} '''!PluginOnlyFailed''' Plugin have found some problems. Tests have not been made. |
| Line 43: | Line 43: |
| {{https://patchbot.sagemath.org/svg/PluginOnly||width=48}} '''!PluginOnly''' Plugins have found no problem. Tests have not been made. {{https://patchbot.sagemath.org/svg/NoPatch||width=48}} '''!NoPatch''' No branch has been uploaded to Trac so far. The patchbot has nothing to do. {{https://patchbot.sagemath.org/svg/Spkg||width=48}} '''Spkg''' This is related to an spkg. The patchbot will only check the spkg installation. |
|
| Line 46: | Line 51: |
| * Detecting which patches to apply are both performed by string searches on each line of the ticket, and are case insensitive. * The patch list directive does not work in ticket descriptions. |
* 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 https://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/sagemath/sage-patchbot.
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 https://patchbot.sagemath.org/ticket/?base=develop&participant=xxxx
For the tickets you authored, see https://patchbot.sagemath.org/ticket/?base=develop&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. The patchbot may have stopped if the ticket was deemed unsafe.
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 branches or dependencies. Try rebase your branch on the latest develop branch.
BuildFailed The branch can be applied, but sage failed to build, due to errors in the code. Check the code.
TestsFailed One or more tests did not succeed.
PluginFailed Tests have been successfully done, but plugins have found some problems.
PluginOnlyFailed Plugin have found some problems. Tests have not been made.
PluginOnly Plugins have found no problem. Tests have not been made.
NoPatch No branch has been uploaded to Trac so far. The patchbot has nothing to do.
Spkg This is related to an spkg. The patchbot will only check the spkg installation.
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