STATUS: FAILED BUILD: master:676fd3f394a0c0576b63c77ed2184bf5f42c29b6 ENVIRONMENT: Ubuntu 12.04 x86_64 STEPS TO REPRODUCE: 1. prepare 2 poky build environments 2. in one of the poky source, set PRSERV_HOST to localhost:0 in local.conf 4. run "bitbake man" and then add following lines into man_${PV}.bb ####### do_package_append() { bb.build.exec_func('do_test_prserv', d) } do_test_prserv() { echo "Test if PR service could work" } ####### 7. re-run "bitbake man", and check the deploy folder if the packages for man are re-generated with PR number bump up 8. run "bitbake-prserv-tool export export.inc" 9. in the second poky source, set PRSERV_HOST to localhost:0 in local.conf 10. copy export.inc into the second poky source's build directory 11. run "bitbake-prserv-tool import export.inc" and run "bitbake man" 12. check the deploy folder if the packages for man are generated with N+1 PR number compared with the first poky source. EXPECTED OUTCOME: Check if AUTOPR could be export/import for package build ACTUAL OUTCOME: packages for man are generated with the same PR number compared with the first poky source.
I will try and reproduce this issue as it seems to be a little more tricky than what is described. As a rough summary, multiple builds must be made in the first poky source that involve adding/removing lines in the man_${PV}.bb file. This stresses the PR server by going back and forth. After exporting and importing the PR server in the second poky source behaves as described in the ACTUAL OUTCOME.
I did try this locally and it worked for me. We therefore need a better set of steps to reproduce and more information where exactly the process fails.
Need more information to help reproduce...
I managed to reproduce this: you have to add the following steps between 10. and 11. 'bitbake -R export.inc man' 'bitbake -cclean man' I will try to find more scenarios that fit this.
Doing the below instead solves the problem: 'bitbake -R export.inc man' 'bitbake -ccleansstate man'
Info provided
The issue is that "bitbake -R export.inc man" will build a package with AUTOPR of "1" yet from metadata which does not match the checksum encoded in the export.inc file. It should have really built a package of "2" yet couldn't due to the data not being in the actual PR Server. I'm not sure this extended test case makes sense. "bitbake -R export.inc man" is not a command that we recommend anywhere in the documentation and it will not behave quite as you'd expect. We only support the use case where data is imported or exported from the PR server, not used in intermediate steps.
https://bugzilla.yoctoproject.org/tr_show_case.cgi?case_id=146 is now marked as DISABLED