| Summary: | Package History: Data Analysis | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] Meta-yocto | Reporter: | Richard Purdie <richard.purdie> |
| Component: | meta-yocto | Assignee: | Paul Eggleton <bluelightning> |
| Status: | VERIFIED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Low | CC: | corneliux.stoicescu, jessica.zhang, jiajun.xu, poky.bs.watcher, poky.watcher, sgw, song.liu |
| Version: | unspecified | ||
| Target Milestone: | 1.2 M2 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | (P1)(QA Testing Completed) (Done) | ||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | --- | |
| Bug Depends on: | 1565 | ||
| Bug Blocks: | |||
|
Description
Richard Purdie
2011-10-03 07:55:13 UTC
Implementation of a command line tool called "buildhistory-diff" to analyse changes in the buildhistory git repo has been merged in revision fcc5f6883c5913d85a98349411ea394045e1f52d. I'm still looking to extend this functionality by implementing a simple web-based flagging tool for 1.2 M3. I think for the feature, QA could design some cases to use the tool "buildhistory-diff" to show changes for recipes. I would like to mark the feature as Test Plan Ready. Paul, if anything more you want QA to cover, pls. tell me. Thanks a lot. I've split off the web part of this to bug #1890, marking this one as resolved. I tried the buildhistory-diff and it could work in M2 build. Verified in master: 09359e6ec00901abfe49157f1f9730117b4d284b |