| Summary: | Tests for forcing a task | ||
|---|---|---|---|
| Product: | [QA/Testing] Build Testing | Reporter: | Paul Eggleton <bluelightning> |
| Component: | general | Assignee: | Daniel Istrate <daniel.alexandrux.istrate> |
| Status: | VERIFIED FIXED | QA Contact: | Alexandru Roman <alexandru.costinx.roman> |
| Severity: | enhancement | ||
| Priority: | Medium | CC: | alexandru.c.georgescu, sgw |
| Version: | unspecified | ||
| Target Milestone: | 2.1 M3 | ||
| Hardware: | All | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
|
Description
Paul Eggleton
2014-02-25 11:12:41 UTC
At the moment we have this test, also automated with oe-selftest, that checks basic functionality of task forcing: https://bugzilla.yoctoproject.org/tr_show_case.cgi?case_id=163 As explained in bug 5805 this was not enough to catch that issue. We will improve upon what we already have to cover the specified scenario. Sent patches to oe-core: http://lists.openembedded.org/pipermail/openembedded-core/2015-October/111485.html Updated TC 163 to match TC 2 and added a new one for TC 1 (https://bugzilla.yoctoproject.org/tr_show_case.cgi?case_id=1354) Verified |