If you are new, you should read about the color codes used by Tinderbox views as well as how to navigate the views.  Otherwise, please proceed by selecting one of the common views:

All builds in the HEAD branch

Errors in the HEAD branch

Errors in the STABLE branch (currently 2.6.x)

All tinderbox builds (currently about 200)

Known Tinderbox issues

At various times, issues arise with the operation of the Tinderbox (as opposed to issues within wxWidgets itself).  Sometimes these issues show up as failed builds, while other issues do not show up in a view but are included below.  This is the current set of all known Tinderbox issues:

Issue dated 2006 Jan 21

The Debian system does not have the GTK development package (which includes the headers and configuration information necessary to compile GTK).  This issue is being tracked in this SourceForge trouble ticket.

Issue dated 2006 Jan 21

The NetBSD headers for pthreads are screwed up, causing wxBase builds to fail.  The issue is being tracked in this SourceForge trouble ticket. 

Issue dated 2004 Jul 30

The wxMac port is no longer supported on OS X 10.1.  There are apparently only two or three problems with this build, so this may be revisited in the future. 

Issue dated 2004 Apr 28

The older OS X box, currently running 10.1, should be upgraded to 10.3 in the next few weeks.  This issue is being tracked by a SourceForge trouble ticket. 

Color codes

The Tinderbox uses colors to highlight the result of a build.  Each color has a specific meaning:

Red (FATAL):

The library itself did not configure, compile, and install successfully.  These are the most critical errors, as a failure in this phase means that there are potentially many developers who cannot proceed until the problem is fixed. 

Orange (ERROR):

The library compiled, but one of the sample, demo, or utility programs did not compile successfully.  This is usually because a change was made to the library and the developer overlooked a program that was affected by the change. 

Yellow (ASAPs):

One or more of the programs failed to compile, but the failing program was marked as something that may not be an error; it should be checked as soon as possible.  These are usually programs that require specific resources that are not available on all sytstems.  An example of this is a program to demonstrate a database being compiled on a system that has no database drivers. 

Green (OK):

Congratulations, everything is working. 

Purple:

These are failures that are due to problems with the machine running the test rather than with wxWidgets.  An example of this would be a machine that didn't have a needed library.  Please let us know on wx-dev if you find a build that should be purple and isn't, or a build that shouldn't be purple and is. 

Navigation

The Tinderbox both provides access to the run logs and can be tailored to focus on a subset of builds that are of interest. 

To see the full log of the test build, click on the link in the second column.  If the build did not succeed, the link in the first column will show the last few lines of the run log so you can quickly see the errors. 

The Tinderbox view can be adjusted to a subset of the available builds.  To narrow the view, click on a link in one of the last three columns to restrict the view to entries with that attribute.  To expand the view again, click on the link in the column header.  To switch between a view of just the builds that failed and all the entries, click on the link at the top of the page.

For example, if you want to know if wxGTK from the current HEAD builds across all platforms, click 'wxGTK' from the 'Toolkit' column then 'HEAD' from the 'CVS Tag' column (or vice versa, both get to the same place).  To narrow the view further to only those builds that failed, click on the link at the top of the page. 

Views may be bookmarked, so if there's a view that you visit frequently, feel free to link to it.