Testing: Difference between revisions

From Openembedded.org
Jump to navigation Jump to search
(→‎Useful software: Added TestingScript by EFfeM)
Line 1: Line 1:
= Overview =
= Overview =


* [http://seAs an example on how to configure your test setup see TestingScriptarch.gmane.org/?query=testing+branch&author=&group=gmane.comp.handhelds.openembedded&sort=date&DEFAULTOP=and&xP=Ztest%09Zbranch&xFILTERS=Gcomp.handhelds.openembedded---A mail list discussions related to the testing branch]
* [http://search.gmane.org/?query=testing+branch&author=&group=gmane.comp.handhelds.openembedded&sort=date&DEFAULTOP=and&xP=Ztest%09Zbranch&xFILTERS=Gcomp.handhelds.openembedded---A mail list discussions related to the testing branch]


The OpenEmbedded Testing branch is a git branch of the OE metadata with the goal of providing a recent snapshot of OE that is known to be build-able for a subset of distros, machines, images, and host workstations.  The goal of this effort is twofold:
The OpenEmbedded Testing branch is a git branch of the OE metadata with the goal of providing a recent snapshot of OE that is known to be build-able for a subset of distros, machines, images, and host workstations.  The goal of this effort is twofold:

Revision as of 10:51, 4 November 2010

Overview

The OpenEmbedded Testing branch is a git branch of the OE metadata with the goal of providing a recent snapshot of OE that is known to be build-able for a subset of distros, machines, images, and host workstations. The goal of this effort is twofold:

  1. the testing branch represents a reasonably stable version of OE that builds for most tested combinations
  2. for all tested combinations, we list the last known-good-build tag so that users can always start with something that will build.

As an example on how to configure your test setup see TestingScript

The test combinations are:

machine distro target workstation bitbake tester last successful build build type Current issues
beagleboard angstrom-2008.1 beagleboard-linuxtag2010-demo-image Ubuntu 10.04 64-bit User:Cbrake testing_2010-10-08 clean failed with: http://tinderbox.openembedded.net/public/logs/task/9261117.txt, fixed with 5203590b8d31271b255be7eae0c115ba47919872
beagleboard angstrom-2008.1 console-image Ubuntu 10.04 64-bit User:Cbrake testing_2010-10-25 clean
bug20 angstrom-2008.1 openjdk-6 Debian Unstable 64-bit 1.10 Stefan testing_2010-10-28 clean
efikamx minimal native-sdk-image Ubuntu 10.10 64-bit User:khem testing_2010-09-27 clean kernel-2.6.31.12-ER1 Error: Package name contains illegal characters, (other than [a-z0-9.+-])
omap5912osk minimal native-sdk-image Ubuntu 10.04 64-bit User:khem testing_2010-10-25 clean
qemuarm minimal native-sdk-image Ubuntu 10.04 64-bit User:khem testing_2010-10-25 clean
qemumips minimal native-sdk-image Ubuntu 10.04 64-bit User:khem testing_2010-10-25 clean
qemuppc minimal native-sdk-image Ubuntu 10.04 64-bit User:khem testing_2010-10-14 clean telnet-netkit: powerpc-oe-linux/bin/ld: final link failed: Nonrepresentable section on output
qemush4 minimal native-sdk-image Ubuntu 10.04 64-bit User:khem testing_2010-09-27 clean Kernel: cc1: error: command line option ‘-m4-nofpu’ is not supported by this configuration
qemux86 minimal native-sdk-image Ubuntu 10.04 64-bit User:khem testing_2010-10-25 clean
qemumipsel minimal x11-image Slackware 13.1 64-bit grg testing_2010-10-14 clean
qemuarm angstrom-2010.x x11-gpe-image Fedora 12 32-bit User:gthomas testing_2010-09-07 clean testing_2010-09-13 fails to build xf86-input-mouse
qemuarm angstrom-2010.x opie-image Fedora 12 32-bit User:gthomas testing_2010-09-07 clean
qemuarm angstrom-2010.x opie-kdepim-image Fedora 12 32-bit User:gthomas None clean fails to build pwmpi
beagleboard angstrom-2008.1 angstrom-gnome-image Ubuntu 9.10 32-bit User:gthomas testing_2010-08-30 clean
beagleboard angstrom-2010.x beagleboard-linuxtag2010-demo-image Fedora 12 32-bit User:gthomas None clean fails to build ti-dsplink if /opt is writeable
qemuarm angstrom-2008.1 x11-gpe-image Fedora 12 32-bit User:gthomas testing_2010-10-04 clean
beagleboard angstrom-2008.1 x11-gpe-image Fedora 12 32-bit User:gthomas testing_2010-10-04 clean
imote2 angstrom-2008.1 imote2-image Gentoo User:jic23 testing_2010-10-29 clean
imote2 angstrom-2010.x imote2-image Gentoo User:jic23 testing_2010-10-29 clean
hipox angstrom-2008.1 minimal-image openSUSE 11.3 32-bit 1.8.18 Sledz [2] testing_2010-10-25 clean
hipox angstrom-2008.1 console-image openSUSE 11.3 32-bit 1.8.18 Sledz [2] testing_2010-10-25 clean
hipox angstrom-2008.1 angstrom-gnome-image openSUSE 11.3 32-bit 1.8.18 Sledz [2] None clean testing_2010-10-14: do_configure epiphany failed
hipox angstrom-2008.1 angstrom-x-image openSUSE 11.3 32-bit 1.8.18 Sledz [2] None clean testing_2010-09-20: do_configure epiphany failed
neek minimal console-image Ubuntu 10.04 64-bit 1.10 eFfeM [1] None clean testing_2010-10-29: fails in libX11: see http://tinderbox.openembedded.net/builds/100734/
nslu2le slugos slugos-image Ubuntu 10.04 64-bit 1.10 eFfeM [1] testing_2010-10-29 clean
nslu2be slugos slugos-image Ubuntu 10.04 64-bit 1.10 eFfeM [1] testing_2010-10-29 clean
calamari minimal console-image Ubuntu 10.04 64-bit 1.10 eFfeM [1] testing_2010-10-29 clean
mpc8313e-rdb minimal console-image Ubuntu 10.04 64-bit 1.10 eFfeM [1] testing_2010-10-29 clean
sheevaplug minimal console-image Ubuntu 10.04 64-bit 1.10 eFfeM [1] testing_2010-10-29 clean
ts72xx angstrom-2008.1 minimal-image Ubuntu 10.04 32-bit master ynezz testing_2010-10-14 clean
ts72xx angstrom-2010.x minimal-image Ubuntu 10.04 32-bit master ynezz testing_2010-10-14 clean Builds only with CFLAGS_append = " -Os" in udev recipe.
overo angstrom-2008.1 meta-toolchain Ubuntu 10.04 64-bit 1.10.0 tharvey testing_2010-10-29 clean QA Issue: gcc
overo angstrom-2008.1 meta-toolchain-qte Ubuntu 10.04 64-bit 1.10.0 tharvey testing_2010-10-29 clean QA Issues: gcc cups
overo angstrom-2008.1 x-load Ubuntu 10.04 64-bit 1.10.0 tharvey testing_2010-10-29 clean
overo angstrom-2008.1 u-boot Ubuntu 10.04 64-bit 1.10.0 tharvey testing_2010-10-29 clean
overo angstrom-2008.1 console-image Ubuntu 10.04 64-bit 1.10.0 tharvey testing_2010-10-29 clean QA Issue: cups
akita angstrom-2008.1 x11-image, opie-image Debian 'Lenny' 5.0.6 x86_64 1.10-git User:Jay7 testing_2010-10-29 clean There should be link to tinderbox
tosa angstrom-2008.1 x11-image, opie-image Debian 'Lenny' 5.0.6 x86_64 1.10-git User:Jay7 testing_2010-10-29 clean There should be link to tinderbox
collie angstrom-2008.1 x11-image, opie-image Debian 'Lenny' 5.0.6 x86_64 1.10-git User:Jay7 testing_2010-10-29 clean There should be link to tinderbox
machine distro target workstation bitbake tester last successful build build type Current issues

[1] Testing done by eFfeM. Resources kindly provided by Axon Digital Design
[2] Testing done by Sledz. Resources kindly provided by DResearch Digital Media Systems GmbH

Testing Procedure

The general process for managing the testing branch is:

  1. Starting at approximately 9PM GMT of every week, the dev.openembedded.org branch is branched to the testing-next branch.
  2. Whoever creates the testing-next branch sends an email to the oe-devel list with a subject of "testing branch YYYY-MM-DD". All volunteers start a clean build and build the combinations they test, update the above chart, and report status/issues as replies to the above email.
  3. If most combinations build by following Thursday, the testing-next branch is merged to the testing branch. Regardless, the repository is tagged with the tested_YYYY-MM-DD tag. An annotated tag is used with a message that includes a text copy of the above table with variations that have been tested building for this cycle. The reason we tag after testing is complete is so that we can include status in the annotated tag. This way information about what was tested with each tagged version is captured in the repository. A link is added for easy reference to the log below.
  4. If a build fails, then issues are reported, and we try to get issues fixed before the next weeks testing cycle.
  5. Not every combination is tested on every cycle, due to availability of testers, so we list the last known built version in the above chart. Testers are responsible for updating the above chart.
  6. All testers are encouraged to use Tinderbox so problems are automatically reported and logged, and issues in the above chart can be linked to Tinderbox.

We strongly encourage chip and SBC/Module vendors to become involved in this effort to ensure OE works for your platforms.

Useful software

Testing Log

Retrieved from "https://www.openembedded.org/w/index.php?title=Testing&oldid=3030"