Test GDB for each new repository commit and report any regressions for it. Test also regressions for user-provided patches.

Regressions get detected by running the thorough GDB testsuite and (a bit fuzzy) comparison of its results against the previous build results. (optional, can be done by the GDB team)



Feature list

Different configs (even within one "build") have different expected fails. It is often easier to maintain expected fails in separate files associated with the config, and use that to assist in report generation.

Compatibility is required with GDB repository in both CVS and GIT.

Support various provided (as rpms, distros or upstream repository branches/tags) GCC versions for building GDB and its testing workload.

Support multiple testing hosts with various architectures. Beaker test system integration must not be required for x86* but it should be supported to be able to cover also other arches.

Support running tests inside various kinds of virtualized hosts. Either mock (=chroot) or the full KVM virtual host. (It may be just provided by Beaker, interfaced probably by libvirt.)

Support running multi-host testsuite using gdbserver (remote GDB backend).

Properly report kernel crashes of hosts under the test. Associate the kernel crash reports with the GDB workload under test.

(optional) Integration with Fedora/RHEL mock (OS distribution provisioning) and the rpm packaging to test also new Fedora/RHEL builds with it.

(optional) Besides GDB to regression test also binutils.

Supporting other features of existing buildbot solutions.

Analyze existing buildbot solutions, we could just deploy one of them:

Hosted Build Services

None: FeaturesForBuildBot (last edited 2014-12-28 23:51:06 by DougEvans)

All content (C) 2008 Free Software Foundation. For terms of use, redistribution, and modification, please see the WikiLicense page.