Bug 6689 - Buildhistory reports no error if recipes go backward
Summary: Buildhistory reports no error if recipes go backward
Status: VERIFIED FIXED
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: configuration (show other bugs)
Version: 1.7
Hardware: x86 Multiple
: Medium+ normal
Target Milestone: 1.7 M3
Assignee: Paul Eggleton
QA Contact: Costin
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2014-09-05 13:53 UTC by Costin
Modified: 2014-09-15 16:21 UTC (History)
1 user (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Don't know


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Costin 2014-09-05 13:53:28 UTC
Hello,

On commit: a44006262cf3b810ec78b4cccd8076102a7a0f3e
Test case 294

Test case content:
"
1. Enable buildhistory in local.conf (add INHERIT += "buildhistory" and BUILDHISTORY_COMMIT = "1")
1. build some recipes and get the buildhistory log(for example, recipe "xcursor-transparent-theme")
2. change the PR of xcursor-transparent-theme backwards, for example from "r4" to "r3"
3. re-build the recipe
"

While doing the above, nothing happens:

output:
...
NOTE: Executing RunQueue Tasks
NOTE: Tasks Summary: Attempted 252 tasks of which 239 didn't need to be rerun and all succeeded.
NOTE: Writing buildhistory

The behavior is similar to bug 5088, only this time meta-yocto/conf/distro/poky.conf contains the necessary version-going-backwards
ERROR_QA = "... version-going-backwards"

I also observed that on a fresh copy of poky without adding PRSERV_HOST = "localhost:0" to local.conf the buildhistory dir is not created.
OS tested on: Ubuntu 14.04 LTS 

Costin
Comment 1 Paul Eggleton 2014-09-10 10:59:19 UTC
I'm pretty sure this is fixed by the following patch, which is out for review:

http://patchwork.openembedded.org/patch/80189/
Comment 3 Costin 2014-09-15 16:21:21 UTC
Hello Paul,

Comming across usual weekly tests, this time for 1.7_MC3_RC2   hash: 429802fe6691c8a70ec9735c0db4c6a4e1e1b038, everything is fine. Issue is solved. I will mark the call as verified.

COstin