Revision as of 10:59, 23 November 2010

Overview

• 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:

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

Test combinations

[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
[3] Testing done by mckoan. Resources kindly provided by Koan sas

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 preferably do an incremental build (from last weeks snapshot), then clean tmp and do a clean build of the combinations they test. If time or resources are not available, then incremental builds are not required. After builds are complete, 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

• Hudson http://hudson-ci.org/
• BuildBot http://buildbot.net/trac
• TestBuilder by Jay7
• TestingScript by EFfeM

Testing Log

• http://cgit.openembedded.org/cgit.cgi/openembedded/tag/?id=testing_2010-08-23
• http://cgit.openembedded.org/cgit.cgi/openembedded/tag/?id=testing_2010-08-30
• http://cgit.openembedded.org/cgit.cgi/openembedded/tag/?id=testing_2010-09-07
• http://cgit.openembedded.org/cgit.cgi/openembedded/tag/?id=testing_2010-09-13
• http://cgit.openembedded.org/cgit.cgi/openembedded/tag/?id=testing_2010-09-20
• http://cgit.openembedded.org/cgit.cgi/openembedded/tag/?id=testing_2010-09-27
• http://cgit.openembedded.org/cgit.cgi/openembedded/tag/?id=testing_2010-10-08
• http://cgit.openembedded.org/cgit.cgi/openembedded/tag/?id=tested_2010-10-14
• http://cgit.openembedded.org/cgit.cgi/openembedded/tag/?id=tested_2010-10-25
• http://cgit.openembedded.org/cgit.cgi/openembedded/tag/?id=tested_2010-10-29