| Summary: |
AUH: run core-image-ptest-${BPN} for testimage (not core-image-sato) |
| Product: |
[Yocto Project Subprojects] Automated Update Handler
|
Reporter: |
Tim Orling <tim.orling> |
| Component: |
Automatic Update Handler | Assignee: |
Tim Orling <tim.orling> |
| Status: |
NEW
---
|
QA Contact: |
apoorv sangal <apoorvsangal> |
| Severity: |
enhancement
|
|
|
| Priority: |
Medium+
|
CC: |
randy.macleod
|
| Version: |
5.1 | |
|
| Target Milestone: |
6.1 M1 | |
|
| Hardware: |
x86 | |
|
| OS: |
Multiple | |
|
| Whiteboard: |
|
|
OS type for building Yocto:
|
---
|
Type of Regression:
|
---
|
|---|
|
Verified:
|
|
Documentation change:
|
Yes (doc changes required)
|
|---|
Not sure that is is currently possible to expand variables in upgrade-helper.conf e.g. # If enabled, build and boots a test image, and runs integration tests on it # If upgraded packages have ptest support those are run as well # # Requires 'testimage' in INHERIT in your conf/local.conf and 'ptest' in your # distro's DISTRO_FEATURES. testimage=yes # This can be used to change the name of the test image. # testimage_name=core-image-ptest-${BPN} Probably the code behind testimage in AUH is not compatible with the concept anyway. But given the new capabilities with the mcextend/BBCLASSEXTEND "magic", it would make the testing of ptest-enabled updates much easier/more useful?