Difference between revisions of "Testing"
From Openembedded.org
(add information on tagging) |
|||
| Line 12: | Line 12: | ||
|bug20 ||angstrom-2008.1 ||openjdk-6 ||Debian Unstable 64-bit ||[[Stefan]] ||testing_2010-08-23 | |bug20 ||angstrom-2008.1 ||openjdk-6 ||Debian Unstable 64-bit ||[[Stefan]] ||testing_2010-08-23 | ||
|- | |- | ||
| − | |efikamx ||minimal ||native-sdk-image ||ubuntu 10.10(Alpha) 64-bit ||[[User:khem]] || testing_2010-08-23 | + | |efikamx ||minimal ||native-sdk-image ||ubuntu 10.10(Alpha) 64-bit ||[[User:khem]] ||testing_2010-08-23 |
|- | |- | ||
|omap5912osk ||minimal-uclibc ||native-sdk-image ||ubuntu 10.10(Alpha) 64-bit ||[[User:khem]] || | |omap5912osk ||minimal-uclibc ||native-sdk-image ||ubuntu 10.10(Alpha) 64-bit ||[[User:khem]] || | ||
| Line 20: | Line 20: | ||
|qemumips ||minimal ||native-sdk-image ||ubuntu 10.10(Alpha) 64-bit ||[[User:khem]] || | |qemumips ||minimal ||native-sdk-image ||ubuntu 10.10(Alpha) 64-bit ||[[User:khem]] || | ||
|- | |- | ||
| − | |qemuppc ||minimal ||native-sdk-image ||ubuntu 10.10(Alpha) 64-bit ||[[User:khem]] || | + | |qemuppc ||minimal ||native-sdk-image ||ubuntu 10.10(Alpha) 64-bit ||[[User:khem]] ||fails to build sed |
|- | |- | ||
| − | |qemux86 ||minimal ||native-sdk-image ||ubuntu 10.10(Alpha) 64-bit ||[[User:khem]] || | + | |qemux86 ||minimal ||native-sdk-image ||ubuntu 10.10(Alpha) 64-bit ||[[User:khem]] ||Fails to build acpid |
|- | |- | ||
| − | |qemumipsel ||minimal ||x11-image ||Slackware 13.1 64-bit ||[[User:grg]] || testing_2010-08-23 | + | |qemumipsel ||minimal ||x11-image ||Slackware 13.1 64-bit ||[[User:grg]] ||testing_2010-08-23 |
|} | |} | ||
Revision as of 06:52, 26 August 2010
The OpenEmbedded Testing branch is a git branch of the OE metadata with the goal of providing a provide a recent snapshot of OE that is known to be build-able for a subset of distros, machines, images, and host workstations. The goal is to provide users with a somewhat tested version of OE that will likely build if they use one of the known working combinations.
The tested combinations tested are:
| machine | distro | target | workstation | tester | last tested version |
|---|---|---|---|---|---|
| beagleboard | angstrom-2008.1 | beagleboard-linuxtag2010-demo-image | Ubuntu 10.04 64-bit | User:Cbrake | testing_2010-08-23 |
| beagleboard | angstrom-2008.1 | console-image | Ubuntu 10.04 64-bit | User:Cbrake | testing_2010-08-23 |
| bug20 | angstrom-2008.1 | openjdk-6 | Debian Unstable 64-bit | Stefan | testing_2010-08-23 |
| efikamx | minimal | native-sdk-image | ubuntu 10.10(Alpha) 64-bit | User:khem | testing_2010-08-23 |
| omap5912osk | minimal-uclibc | native-sdk-image | ubuntu 10.10(Alpha) 64-bit | User:khem | |
| qemuarm | minimal | native-sdk-image | ubuntu 10.10(Alpha) 64-bit | User:khem | |
| qemumips | minimal | native-sdk-image | ubuntu 10.10(Alpha) 64-bit | User:khem | |
| qemuppc | minimal | native-sdk-image | ubuntu 10.10(Alpha) 64-bit | User:khem | fails to build sed |
| qemux86 | minimal | native-sdk-image | ubuntu 10.10(Alpha) 64-bit | User:khem | Fails to build acpid |
| qemumipsel | minimal | x11-image | Slackware 13.1 64-bit | User:grg | testing_2010-08-23 |
The general process for managing the testing branch is:
- starting on Monday of every week, the dev.openembedded.org branch is branched to the testing-testing branch.
- whoever creates the testing-testing branch sends an email to the oe-devel list with a subject of "testing branch YYYY-MM-DD". All volunteers start clean builds for the combinations they test, and report status as replies to the above email.
- if no issues are reported by the following Monday, the testing-testing branch is merged to the testing branch, and the testing_YYYY-MM-DD tag is applied. An annotated tag is used with a message that includes a text copy of the above table with variations that have been tested working for this cycle. This way information about what was tested with each tagged version is captured in the repository.
- if a build fails, then issues are reported, and the testing-testing branch is moved ahead to capture fixes made in the dev branch. Once the issue is fixed, all combinations are retested.
- Not every combination is tested on every cycle, due to availability of testers, so we list the last known version in the above chart. Testers are responsible for updating the above chart.
We strongly encourage chip and SBC/Module vendors to become involved in this effort to ensure OE works for your platforms.
