Size: 2528
Comment: better formatting
|
Size: 3186
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 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: |
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, populate the dependencies field with the ticket numbers and/or minimal sage version. | For the tickets you participated in, see https://patchbot.sagemath.org/ticket/?base=develop&participant=xxxx |
Line 22: | Line 21: |
Only the devel repository has branches, so the patchbot is unable to apply and try out patches to extcode/scripts/etc. | For the tickets you authored, see https://patchbot.sagemath.org/ticket/?base=develop&author=xxxx |
Line 24: | Line 23: |
=== Possible status === | === Ticket Status === |
Line 26: | Line 25: |
Patches can have the following 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: |
Line 28: | Line 27: |
* New (grey) | {{https://patchbot.sagemath.org/svg/New||width=48}} '''New''' |
Line 30: | Line 29: |
* ApplyFailed (red) The patch could not be applied. This can be caused by conflicts with other patches or dependencies. | {{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 32: | Line 31: |
* BuildFailed () | {{https://patchbot.sagemath.org/svg/TestsPassed||width=48}} '''!TestsPassed''' Everything is okay, as far as a patchbot can tell. |
Line 34: | Line 33: |
* TestsFailed (yellow) Some tests did not succeed. They can be found in the report of the bot. | {{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 36: | Line 35: |
* PluginFailed (blue) Documentation and commit messages should be checked. See the report to see what is wrong. | {{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 38: | Line 37: |
* TestsPassed (green) Everything is ok, as far as the bot can tell. | {{https://patchbot.sagemath.org/svg/TestsFailed||width=48}} '''!TestsFailed''' One or more tests did not succeed. |
Line 40: | Line 39: |
* Pending (grey) The bot is currently running on this patch. | {{https://patchbot.sagemath.org/svg/PluginFailed||width=48}} '''!PluginFailed''' Tests have been successfully done, but plugins have found some problems. |
Line 42: | Line 41: |
* NoPatch () No patch has been uploaded to trac so far. | {{https://patchbot.sagemath.org/svg/PluginOnlyFailed||width=48}} '''!PluginOnlyFailed''' Plugin have found some problems. Tests have not been made. |
Line 44: | Line 43: |
* Spkg (purple) This is not related to a patch but to a spkg package. | {{https://patchbot.sagemath.org/svg/PluginOnly||width=48}} '''!PluginOnly''' Plugins have found no problem. Tests have not been made. |
Line 46: | Line 45: |
{{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 49: | Line 51: |
Detecting 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 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/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 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