Bug 12740 - [master-next] multiple build failures for same dnf issue in sanity tests
Summary: [master-next] multiple build failures for same dnf issue in sanity tests
Status: RESOLVED FIXED
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: core (show other bugs)
Version: 2.6
Hardware: x86 Multiple
: Medium normal
Target Milestone: 2.6
Assignee: Richard Purdie
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2018-05-09 17:18 UTC by Armin Kuster
Modified: 2018-06-28 14:10 UTC (History)
2 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: New (Never tested)
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 Armin Kuster 2018-05-09 17:18:38 UTC
it appears the same failure occurred on multiple "Running Sanity tests"

NOTE: core-image-lsb-1.0-r0 do_testimage: FAIL [3.630s]: test_parselogs (parselogs.ParseLogsTest)
NOTE: core-image-lsb-1.0-r0 do_testimage: ----------------------------------------------------------------------
NOTE: core-image-lsb-1.0-r0 do_testimage: Traceback (most recent call last):
  File "/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-x86-64-lsb/build/meta/lib/oeqa/core/decorator/__init__.py", line 32, in wrapped_f
    return func(*args, **kwargs)
  File "/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-x86-64-lsb/build/meta/lib/oeqa/core/decorator/__init__.py", line 32, in wrapped_f
    return func(*args, **kwargs)
  File "/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-x86-64-lsb/build/meta/lib/oeqa/runtime/cases/parselogs.py", line 363, in test_parselogs
    self.assertEqual(errcount, 0, msg=self.msg)
AssertionError: 1 != 0 : Log: /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-x86-64-lsb/build/build/tmp/work/qemux86_64-poky-linux/core-image-lsb/1.0-r0/dnf.rpm.log
-----------------------
Central error: 2018-05-09T22:08:33Z ERROR Non-fatal POSTIN scriptlet failure in rpm package busybox
Comment 1 Richard Purdie 2018-06-28 14:10:31 UTC
This was in -next and the patches in question were revised and fixed before they were merged.