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 .

Patch Buildbot (Patchbot)

The second pulls and applies git branches from Trac and can be found at 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 Eventually this will get moved into Sage where it can be edited using the standard procedures and more widely deployed. See ticket

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

For the tickets you authored, see

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

buildbot (last edited 2015-11-08 17:25:45 by chapoton)