stdcxx-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Martin Sebor <>
Subject Re: Buildbot - Useful for nightly testing?
Date Sun, 07 Jun 2009 23:42:17 GMT
Gavin wrote:
> Hi All,

Hi Gavin!

> I noticed from the last board report that you are looking for a
> replacement(s) for nightly testing.
> We have a Buildbot instance at &&
> .
> I have seen some of your test results at and these
> look comprehensive. Whilst Buildbot may not be as thorough with producing
> results I hope that it can help in some way with your build testing.
> Currently Buildbot is only available on Ubuntu. There are plans to expand
> the build farm and so Buildbot will be available on other platforms over the
> next few months.
> Some questions if I can.
> 1. Interested?


> 2. Id like to test Stdcxx on Buildbot on our Ubuntu machine, can someone run
> through what simple tests we can run for now? - I'll about getting it on
> there over the next few days.

I'll be interested in looking at the results. I'll need some time
to better understand the current presentation format.

> 3. I would like a summary of what you would need to replicate either your
> current build/test setup, or what you believe would be good to have at
> Apache for your needs - consider that no machine is likely to be dedicated
> to one project, but rather shared in a way to benefit all. Mention any
> features of post-build outcomes you have or desire also.

The stdcxx builds pages present the build and test results across
the set of tested configurations of the project on each platform
(a unique combination of compiler, operating system, and hardware

For example, the page below consists of 5 tables showing the build
and test results of 16 configurations of stdcxx with gcc 4.1.1 on
Solaris 10/SPARC:

The first table, Logs and Columns (,
gives summary info about each build (the OS, hardware architecture,
compiler, the "build type" -- see the last table on the page, titled
Build Types), how old the build result is (WRT the date the page was
created), the svn revision the result corresponds to, the sizes of
various artifacts of the build process, and the number of diagnostics
issued during each stage of the build process.

The second table, Timings ( gives
timings of the stages of the build process.

The next three tables, titled "Results of %d %s from %d logs" show
the results of compiling, linking, and running each of stdcxx tests
(those are divided into tests of locales, unit tests, and example
programs supplied with the project). Every row in each of these
tables represents a single test. Every column corresponds to each
of the builds (configurations) of the project. The cell format,
including the color scheme, is documented in a table titled Codes
and Colors toward the bottom of the page (see Only rows with "interesting"
results (i.e., those indicating a problem of some kind) are shown.

The pages are generated from plain text logs created by the build
and test script distributed with stdcxx:

The script responsible for generating the pages is xbuildgen:


> Whilst I couldn't guarantee anything, I would like to take this to
> infrastructure and use it in consideration when planning our purchasing
> requirements for the build farm expansion.
> Thanks
> Gav...

View raw message