| Summary: |
Regularly run checkpkg on yocto autobuilder |
| Product: |
[Infrastructure] AutoBuilder
|
Reporter: |
Joshua Lock <joshuagloe> |
| Component: |
autobuilder | Assignee: |
Alexander Kanavin <alex.kanavin> |
| Status: |
RESOLVED
FIXED
|
QA Contact: |
|
| Severity: |
enhancement
|
|
|
| Priority: |
Medium
|
CC: |
alex.kanavin, infras.ab.watcher, Infras.watcher, pidge
|
| Version: |
2.3 | |
|
| Target Milestone: |
2.4 M2 | |
|
| Hardware: |
x86 | |
|
| OS: |
Multiple | |
|
| Whiteboard: |
|
|
OS type for building Yocto:
|
---
|
Type of Regression:
|
---
|
|---|
|
Verified:
|
|
Documentation change:
|
No (bug/feature does not impact docs)
|
|---|
We want to avoid changes to OE-Core which cause checkpkg to fail, and thus prevent recipe reporting tool from being able to reliably do its work for the recipe in question. We should add functionality to yocto-autobuilder to regularly run the checkpkg task. Suggested steps from Alexander on the mailing list: > - run bitbake -c checkpkg world > - inspect tmp/log/checkpkg.csv for lines with 'UNKNOWN' upstream > status, > make a list of recipes that have it > - compare that list against a stored list of exceptions (currently > it > would have about 32 entries), if the lists don't match exactly, the > upstream version check has failed. > > All of this can be wrapped in poky/scripts/upstream-check-all > perhaps.