Bug 12647

Summary: [2.5 M3 rc1][OE-Core:Debian9] recipe xcursor-transport-theme went backwards, breaks package feeds
Product: [QA/Testing] Build Testing Reporter: Aaron Chan <aaron.chun.yew.chan>
Component: generalAssignee: Paul Eggleton <bluelightning>
Status: RESOLVED FIXED QA Contact: Aaron Chan <aaron.chun.yew.chan>
Severity: normal    
Priority: High CC: aaron.chun.yew.chan, apoorv.sangal, ee.peng.yeoh, randy.macleod, richard.purdie, ross.burton, stephano
Version: 2.5   
Target Milestone: 2.5 M4   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: Regression (Found by QA test)
Verified: Documentation change: Don't know
Attachments:
Description Flags
Package version xcursor-transparent-theme went backwards which could break package feeds
none
qa.log after removing INHERIT += "rm_work"
none
[2.5 M3 rc1] - Build 49 - Debian9 - Oe-selftest none

Description Aaron Chan 2018-04-04 00:22:52 UTC
Created attachment 4256 [details]
Package version xcursor-transparent-theme went backwards which could break package feeds

========================================================================================================================================
Bitbake (core-image-minimal)
========================================================================================================================================
Build Configuration:
BB_VERSION           = "1.37.0"
BUILD_SYS            = "x86_64-linux"
NATIVELSBSTRING      = "debian-9"
TARGET_SYS           = "i586-poky-linux"
MACHINE              = "qemux86"
DISTRO               = "poky"
DISTRO_VERSION       = "2.4+snapshot-20180328"
TUNE_FEATURES        = "m32 i586"
TARGET_FPU           = ""
meta                 
meta-poky            
meta-yocto-bsp       = "heads/master:f49ee61422c867516db252054e993df29f775136"

========================================================================================================================================
TESTCASES: (Cound not find stamp for task do_package for recipe xcursor-transparent-theme/m4)
========================================================================================================================================
2018-03-29 01:24:59,754 - oe-selftest - INFO - RESULTS - prservice.BitbakePrTests.test_pr_service_deb_arch_dep - Testcase 934: FAILED
2018-03-29 01:24:59,754 - oe-selftest - INFO - RESULTS - prservice.BitbakePrTests.test_pr_service_deb_arch_indep - Testcase 937: FAILED
2018-03-29 01:24:59,755 - oe-selftest - INFO - RESULTS - prservice.BitbakePrTests.test_pr_service_ipk_arch_dep - Testcase 933: FAILED
2018-03-29 01:24:59,755 - oe-selftest - INFO - RESULTS - prservice.BitbakePrTests.test_pr_service_ipk_arch_indep - Testcase 936: FAILED
2018-03-29 01:24:59,755 - oe-selftest - INFO - RESULTS - prservice.BitbakePrTests.test_pr_service_rpm_arch_dep - Testcase 932: FAILED
2018-03-29 01:24:59,755 - oe-selftest - INFO - RESULTS - prservice.BitbakePrTests.test_pr_service_rpm_arch_indep - Testcase 935: FAILED

========================================================================================================================================
ASSERTION ERROR:
========================================================================================================================================
2018-04-02 11:03:14,783 - oe-selftest - INFO - ======================================================================
2018-04-02 11:03:14,783 - oe-selftest - INFO - FAIL [22.064s]: test_pr_service_ipk_arch_indep (prservice.BitbakePrTests)
2018-04-02 11:03:14,784 - oe-selftest - INFO - FAIL [22.025s]: test_pr_service_rpm_arch_indep (prservice.BitbakePrTests)
2018-04-02 11:03:14,782 - oe-selftest - INFO - FAIL [22.633s]: test_pr_service_deb_arch_indep (prservice.BitbakePrTests)
2018-04-02 11:03:14,783 - oe-selftest - INFO - ----------------------------------------------------------------------
2018-04-02 11:03:14,783 - oe-selftest - INFO - Traceback (most recent call last):
  File "/home/ab/autobuilder/yocto-worker/nightly-oe-selftest-debian9/build/meta/lib/oeqa/core/decorator/__init__.py", line 32, in wrapped_f
    return func(*args, **kwargs)
  File "/home/ab/autobuilder/yocto-worker/nightly-oe-selftest-debian9/build/meta/lib/oeqa/selftest/cases/prservice.py", line 121, in test_pr_service_ipk_arch_indep
    self.run_test_pr_service('xcursor-transparent-theme', 'ipk', 'do_package')
  File "/home/ab/autobuilder/yocto-worker/nightly-oe-selftest-debian9/build/meta/lib/oeqa/selftest/cases/prservice.py", line 57, in run_test_pr_service
    stamp_1 = self.get_task_stamp(package_name, track_task)
  File "/home/ab/autobuilder/yocto-worker/nightly-oe-selftest-debian9/build/meta/lib/oeqa/selftest/cases/prservice.py", line 35, in get_task_stamp
    self.assertFalse(len(stamps) == 0, msg="Cound not find stamp for task %s for recipe %s" % (recipe_task, package_name))
AssertionError: True is not false : Cound not find stamp for task do_package for recipe xcursor-transparent-theme

========================================================================================================================================
Package version for package xcursor-transparent-theme-doc went backwards
========================================================================================================================================
Link: http://centaurus01.png.intel.com:8080/workspace/debian9/nightly-oe-selftest-debian9/build/build/tmp/qa.log

xcursor-transparent-theme-0.1.1+gitAUTOINC+23c8af5ba4: Package version for package xcursor-transparent-theme-dbg went backwards which would break package feeds from (0:0.1.1+git0+23c8af5ba4-r1 to 0:0.1.1+git0+23c8af5ba4-r0) [version-going-backwards]
xcursor-transparent-theme-0.1.1+gitAUTOINC+23c8af5ba4: Package version for package xcursor-transparent-theme-staticdev went backwards which would break package feeds from (0:0.1.1+git0+23c8af5ba4-r1 to 0:0.1.1+git0+23c8af5ba4-r0) [version-going-backwards]
xcursor-transparent-theme-0.1.1+gitAUTOINC+23c8af5ba4: Package version for package xcursor-transparent-theme-dev went backwards which would break package feeds from (0:0.1.1+git0+23c8af5ba4-r1 to 0:0.1.1+git0+23c8af5ba4-r0) [version-going-backwards]
xcursor-transparent-theme-0.1.1+gitAUTOINC+23c8af5ba4: Package version for package xcursor-transparent-theme-doc went backwards which would break package feeds from (0:0.1.1+git0+23c8af5ba4-r1 to 0:0.1.1+git0+23c8af5ba4-r0) [version-going-backwards]
xcursor-transparent-theme-0.1.1+gitAUTOINC+23c8af5ba4: Package version for package xcursor-transparent-theme-locale went backwards which would break package feeds from (0:0.1.1+git0+23c8af5ba4-r1 to 0:0.1.1+git0+23c8af5ba4-r0) [version-going-backwards]
xcursor-transparent-theme-0.1.1+gitAUTOINC+23c8af5ba4: Package version for package xcursor-transparent-theme went backwards which would break package feeds from (0:0.1.1+git0+23c8af5ba4-r1 to 0:0.1.1+git0+23c8af5ba4-r0) [version-going-backwards]
xcursor-transparent-theme-0.1.1+gitAUTOINC+23c8af5ba4: xcursor-transparent-theme-dbg is listed in PACKAGES multiple times, this leads to packaging errors. [packages-list]
xcursor-transparent-theme-0.1.1+gitAUTOINC+23c8af5ba4: xcursor-transparent-theme-dbg is listed in PACKAGES multiple times, this leads to packaging errors. [packages-list]
emptytest-1.0: emptytest: The LIC_FILES_CHKSUM does not match for file:///tmp/tmp52nabg7i;md5=d41d8cd98f00b204e9800998ecf8427e
emptytest: The new md5 checksum is 8d777f385d3dfec8815d20f7496026dc
emptytest: Here is the selected license text:
vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv
data
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
emptytest: Check if the license information has changed in /tmp/tmp52nabg7i to verify that the LICENSE value "" remains valid [license-checksum]
xcursor-transparent-theme-0.1.1+gitAUTOINC+23c8af5ba4: Package version for package xcursor-transparent-theme-dbg went backwards which would break package feeds from (0:0.1.1+git0+23c8af5ba4-r1 to 0:0.1.1+git0+23c8af5ba4-r0) [version-going-backwards]
xcursor-transparent-theme-0.1.1+gitAUTOINC+23c8af5ba4: Package version for package xcursor-transparent-theme-staticdev went backwards which would break package feeds from (0:0.1.1+git0+23c8af5ba4-r1 to 0:0.1.1+git0+23c8af5ba4-r0) [version-going-backwards]
xcursor-transparent-theme-0.1.1+gitAUTOINC+23c8af5ba4: Package version for package xcursor-transparent-theme-dev went backwards which would break package feeds from (0:0.1.1+git0+23c8af5ba4-r1 to 0:0.1.1+git0+23c8af5ba4-r0) [version-going-backwards]
xcursor-transparent-theme-0.1.1+gitAUTOINC+23c8af5ba4: Package version for package xcursor-transparent-theme-doc went backwards which would break package feeds from (0:0.1.1+git0+23c8af5ba4-r1 to 0:0.1.1+git0+23c8af5ba4-r0) [version-going-backwards]
xcursor-transparent-theme-0.1.1+gitAUTOINC+23c8af5ba4: Package version for package xcursor-transparent-theme-locale went backwards which would break package feeds from (0:0.1.1+git0+23c8af5ba4-r1 to 0:0.1.1+git0+23c8af5ba4-r0) [version-going-backwards]
xcursor-transparent-theme-0.1.1+gitAUTOINC+23c8af5ba4: Package version for package xcursor-transparent-theme went backwards which would break package feeds from (0:0.1.1+git0+23c8af5ba4-r1 to 0:0.1.1+git0+23c8af5ba4-r0) [version-going-backwards]
Comment 1 Paul Eggleton 2018-04-08 13:33:07 UTC
Looks like the PR service might not be doing its job in this instance, since it's supposed to be ensuring that the version increases in this scenario.
Comment 2 Paul Eggleton 2018-04-16 21:26:31 UTC
The "Could not find stamp for task do_package .." part of this is likely a follow-on from rm_work as we found for bug 12655, and were reproducible. The "version going backwards" failures are not reproducible on either debian 9 or opensuse 42.3, earlier apparently those errors were seen on multiple host OSes, not just on debian 9. Aaron is re-running a full build to see if the errors are still shown.
Comment 3 Aaron Chan 2018-04-16 22:13:38 UTC
===============================================================================
REPRODUCE ERRORS
===============================================================================
The issue was found to be reproducible with the INHERIT += "rm_work" set on the build/conf/auto.conf file.

{'CreateAutoConf': {'machine': 'qemux86-64', 'SDKMACHINE' : 'x86_64',
                    'distro': 'poky', 'nosstate': True,
                    'packages': 'rpm', 'buildhistory' : False,
                    'prserv': False,
                    'atextappend': 'RPM_GPG_SIGN_CHUNK = "1"\nINHERIT += "rm_work"\n'}},

STEPS:
$ cd ~/yocto-worker/nightly-oe-selftest-debian9/build
$ source oe-init-build-env
$ oe-selftest -r prservice.BitbakePrTests

===============================================================================
ISSUE RESOLVED
===============================================================================

Omit the INHERIT += "rm_work" from the build/conf/auto.conf. Refer to link below:

http://centaurus01.png.intel.com:8080/workspace/ab-controller/buildset-config/nightly-oe-selftest-debian9.conf

Rerun the same steps as above to manually verify the issues goes away.

===============================================================================
DEBIAN-9 RERUN ON 2.5 MR RC1 below:
===============================================================================

http://centaurus01.png.intel.com:8010/builders/nightly-oe-selftest-debian9/builds/48
Comment 4 Aaron Chan 2018-04-17 04:25:56 UTC
From the logs http://centaurus01.png.intel.com:8010/builders/nightly-oe-selftest-debian9/builds/48/steps/Running%20oe-selftest/logs/stdio

it appears the prservice.BitbakePrTests seems to be passing and issue was resolved after INHERIT += "rm_work" has been
removed during AutoConf Buildstep generated by Autobuilder.

2018-04-17 14:36:00,161 - oe-selftest - INFO - RESULTS - pkgdata.OePkgdataUtilTests.test_specify_pkgdatadir - Testcase 1206: PASSED
2018-04-17 14:36:00,161 - oe-selftest - INFO - RESULTS - prservice.BitbakePrTests.test_import_export_override_db - Testcase 931: PASSED
2018-04-17 14:36:00,161 - oe-selftest - INFO - RESULTS - prservice.BitbakePrTests.test_import_export_replace_db - Testcase 930: PASSED
2018-04-17 14:36:00,161 - oe-selftest - INFO - RESULTS - prservice.BitbakePrTests.test_pr_service_deb_arch_dep - Testcase 934: PASSED
2018-04-17 14:36:00,162 - oe-selftest - INFO - RESULTS - prservice.BitbakePrTests.test_pr_service_deb_arch_indep - Testcase 937: PASSED
2018-04-17 14:36:00,162 - oe-selftest - INFO - RESULTS - prservice.BitbakePrTests.test_pr_service_ipk_arch_dep - Testcase 933: PASSED
2018-04-17 14:36:00,162 - oe-selftest - INFO - RESULTS - prservice.BitbakePrTests.test_pr_service_ipk_arch_indep - Testcase 936: PASSED
2018-04-17 14:36:00,162 - oe-selftest - INFO - RESULTS - prservice.BitbakePrTests.test_pr_service_rpm_arch_dep - Testcase 932: PASSED
2018-04-17 14:36:00,162 - oe-selftest - INFO - RESULTS - prservice.BitbakePrTests.test_pr_service_rpm_arch_indep - Testcase 935: PASSED
2018-04-17 14:36:00,163 - oe-selftest - INFO - RESULTS - prservice.BitbakePrTests.test_stopping_prservice_message - Testcase 1419: PASSED
2018-04-17 14:36:00,163 - oe-selftest - INFO - RESULTS - recipetool.RecipetoolAppendsrcTests.test_recipetool_appendsrcfile_basic - Testcase 1273: PASSED
Comment 5 Aaron Chan 2018-04-17 04:29:40 UTC
From the logs http://centaurus01.png.intel.com:8010/builders/nightly-oe-selftest-debian9/builds/48/steps/Running%20oe-selftest/logs/stdio

it appears the prservice.BitbakePrTests seems to be passing and issue was resolved after INHERIT += "rm_work" has been
removed during AutoConf Buildstep generated by Autobuilder.

2018-04-17 14:36:00,161 - oe-selftest - INFO - RESULTS - pkgdata.OePkgdataUtilTests.test_specify_pkgdatadir - Testcase 1206: PASSED
2018-04-17 14:36:00,161 - oe-selftest - INFO - RESULTS - prservice.BitbakePrTests.test_import_export_override_db - Testcase 931: PASSED
2018-04-17 14:36:00,161 - oe-selftest - INFO - RESULTS - prservice.BitbakePrTests.test_import_export_replace_db - Testcase 930: PASSED
2018-04-17 14:36:00,161 - oe-selftest - INFO - RESULTS - prservice.BitbakePrTests.test_pr_service_deb_arch_dep - Testcase 934: PASSED
2018-04-17 14:36:00,162 - oe-selftest - INFO - RESULTS - prservice.BitbakePrTests.test_pr_service_deb_arch_indep - Testcase 937: PASSED
2018-04-17 14:36:00,162 - oe-selftest - INFO - RESULTS - prservice.BitbakePrTests.test_pr_service_ipk_arch_dep - Testcase 933: PASSED
2018-04-17 14:36:00,162 - oe-selftest - INFO - RESULTS - prservice.BitbakePrTests.test_pr_service_ipk_arch_indep - Testcase 936: PASSED
2018-04-17 14:36:00,162 - oe-selftest - INFO - RESULTS - prservice.BitbakePrTests.test_pr_service_rpm_arch_dep - Testcase 932: PASSED
2018-04-17 14:36:00,162 - oe-selftest - INFO - RESULTS - prservice.BitbakePrTests.test_pr_service_rpm_arch_indep - Testcase 935: PASSED
2018-04-17 14:36:00,163 - oe-selftest - INFO - RESULTS - prservice.BitbakePrTests.test_stopping_prservice_message - Testcase 1419: PASSED
2018-04-17 14:36:00,163 - oe-selftest - INFO - RESULTS - recipetool.RecipetoolAppendsrcTests.test_recipetool_appendsrcfile_basic - Testcase 1273: PASSED
Comment 6 Aaron Chan 2018-04-17 04:32:23 UTC
Created attachment 4271 [details]
qa.log after removing INHERIT += "rm_work"
Comment 7 Aaron Chan 2018-04-17 04:35:37 UTC
Although some issues has been resolve, however the warning for package feeds for xcursor-transparent-theme still go backwards. 
Need more info to investigate this further.

=================================================================================================================
Refer to the reference link below or the attachment in this ticket "qa.log after removing INHERIT += "rm_work"
http://centaurus01.png.intel.com:8080/workspace/debian9/nightly-oe-selftest-debian9/build/build/tmp/qa.log
=================================================================================================================

xcursor-transparent-theme-0.1.1+gitAUTOINC+23c8af5ba4: Package version for package xcursor-transparent-theme-dbg went backwards which would break package feeds from (0:0.1.1+git0+23c8af5ba4-r1 to 0:0.1.1+git0+23c8af5ba4-r0) [version-going-backwards]
xcursor-transparent-theme-0.1.1+gitAUTOINC+23c8af5ba4: Package version for package xcursor-transparent-theme-staticdev went backwards which would break package feeds from (0:0.1.1+git0+23c8af5ba4-r1 to 0:0.1.1+git0+23c8af5ba4-r0) [version-going-backwards]
xcursor-transparent-theme-0.1.1+gitAUTOINC+23c8af5ba4: Package version for package xcursor-transparent-theme-dev went backwards which would break package feeds from (0:0.1.1+git0+23c8af5ba4-r1 to 0:0.1.1+git0+23c8af5ba4-r0) [version-going-backwards]
xcursor-transparent-theme-0.1.1+gitAUTOINC+23c8af5ba4: Package version for package xcursor-transparent-theme-doc went backwards which would break package feeds from (0:0.1.1+git0+23c8af5ba4-r1 to 0:0.1.1+git0+23c8af5ba4-r0) [version-going-backwards]
xcursor-transparent-theme-0.1.1+gitAUTOINC+23c8af5ba4: Package version for package xcursor-transparent-theme-locale went backwards which would break package feeds from (0:0.1.1+git0+23c8af5ba4-r1 to 0:0.1.1+git0+23c8af5ba4-r0) [version-going-backwards]
xcursor-transparent-theme-0.1.1+gitAUTOINC+23c8af5ba4: Package version for package xcursor-transparent-theme went backwards which would break package feeds from (0:0.1.1+git0+23c8af5ba4-r1 to 0:0.1.1+git0+23c8af5ba4-r0) [version-going-backwards]
xcursor-transparent-theme-0.1.1+gitAUTOINC+23c8af5ba4: xcursor-transparent-theme-dbg is listed in PACKAGES multiple times, this leads to packaging errors. [packages-list]
xcursor-transparent-theme-0.1.1+gitAUTOINC+23c8af5ba4: xcursor-transparent-theme-dbg is listed in PACKAGES multiple times, this leads to packaging errors. [packages-list]
emptytest-1.0: emptytest: The LIC_FILES_CHKSUM does not match for file:///tmp/tmpojkp2dcs;md5=d41d8cd98f00b204e9800998ecf8427e
emptytest: The new md5 checksum is 8d777f385d3dfec8815d20f7496026dc
emptytest: Here is the selected license text:
vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv
data
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
emptytest: Check if the license information has changed in /tmp/tmpojkp2dcs to verify that the LICENSE value "" remains valid [license-checksum]
xcursor-transparent-theme-0.1.1+gitAUTOINC+23c8af5ba4: Package version for package xcursor-transparent-theme-dbg went backwards which would break package feeds from (0:0.1.1+git0+23c8af5ba4-r1 to 0:0.1.1+git0+23c8af5ba4-r0) [version-going-backwards]
xcursor-transparent-theme-0.1.1+gitAUTOINC+23c8af5ba4: Package version for package xcursor-transparent-theme-staticdev went backwards which would break package feeds from (0:0.1.1+git0+23c8af5ba4-r1 to 0:0.1.1+git0+23c8af5ba4-r0) [version-going-backwards]
xcursor-transparent-theme-0.1.1+gitAUTOINC+23c8af5ba4: Package version for package xcursor-transparent-theme-dev went backwards which would break package feeds from (0:0.1.1+git0+23c8af5ba4-r1 to 0:0.1.1+git0+23c8af5ba4-r0) [version-going-backwards]
xcursor-transparent-theme-0.1.1+gitAUTOINC+23c8af5ba4: Package version for package xcursor-transparent-theme-doc went backwards which would break package feeds from (0:0.1.1+git0+23c8af5ba4-r1 to 0:0.1.1+git0+23c8af5ba4-r0) [version-going-backwards]
xcursor-transparent-theme-0.1.1+gitAUTOINC+23c8af5ba4: Package version for package xcursor-transparent-theme-locale went backwards which would break package feeds from (0:0.1.1+git0+23c8af5ba4-r1 to 0:0.1.1+git0+23c8af5ba4-r0) [version-going-backwards]
xcursor-transparent-theme-0.1.1+gitAUTOINC+23c8af5ba4: Package version for package xcursor-transparent-theme went backwards which would break package feeds from (0:0.1.1+git0+23c8af5ba4-r1 to 0:0.1.1+git0+23c8af5ba4-r0) [version-going-backwards]
Comment 8 Aaron Chan 2018-04-17 18:47:25 UTC
Rerun the 2.5 M3 rc1 and resolved all the issues on OE-selftest 

http://centaurus01.png.intel.com:8010/builders/nightly-oe-selftest-debian9/builds/49

The results on the Oe-selftest is attach in this ticket, filename as "oe-selftest-results-20180417162910.log", however the Package version xcursor-transparent-theme backwards warnings still exists.
Comment 9 Aaron Chan 2018-04-17 18:48:30 UTC
Created attachment 4273 [details]
[2.5 M3 rc1] - Build 49 - Debian9 - Oe-selftest
Comment 10 Paul Eggleton 2018-04-18 14:44:18 UTC
Richard pointed out that buildoptions.BuildhistoryTests.test_buildhistory_buildtime_pr_backwards intentionally triggers this QA issue in order to check that it actually works, so we would expect to see the results of that in qa.log. On the fairly safe assumption that that is in fact what we're seeing, I think we can consider that the presence of those warnings isn't a bug.