Bug 12978 - Error in oeqa not casing build to fail
Summary: Error in oeqa not casing build to fail
Status: CLOSED FIXED
Alias: None
Product: AutoBuilder
Classification: Infrastructure
Component: autobuilder (show other bugs)
Version: 2.6
Hardware: x86 Multiple
: Medium+ normal
Target Milestone: 2.7 M1
Assignee: Armin Kuster
QA Contact:
URL: https://autobuilder.yoctoproject.org/...
Whiteboard:
Depends on:
Blocks:
 
Reported: 2018-11-02 01:47 UTC by Armin Kuster
Modified: 2019-01-17 14:54 UTC (History)
4 users (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 Armin Kuster 2018-11-02 01:47:56 UTC
error: setUpClass (signing.Signing) [
Traceback (most recent call last):
  File "/home/pokybuild/yocto-worker/nightly-oe-selftest/build/meta/lib/oeqa/core/case.py", line 32, in _oeSetUpClass
    clss.setUpClassMethod()
  File "/home/pokybuild/yocto-worker/nightly-oe-selftest/build/meta/lib/oeqa/selftest/cases/signing.py", line 23, in setUpClass
    raise AssertionError("This test needs GnuPG")
AssertionError: This test needs GnuPG
]
Comment 1 Armin Kuster 2018-11-02 16:03:14 UTC
is this the desired behavior or should the test fail?
Comment 3 Armin Kuster 2018-11-10 02:29:44 UTC
(In reply to comment #2)
> http://git.yoctoproject.org/cgit.cgi/poky/commit/
> ?id=1110b68dda41f5cdc849ec01afff5c4b45cd90aa maybe?

this failed on master.
Comment 4 Armin Kuster 2018-11-13 16:42:21 UTC
This was found on master so moving version. Need a new master build to double check
Comment 5 Richard Purdie 2018-11-15 16:42:15 UTC
This error this bug links to is a master build but doesn't appear to have this failure?
Comment 6 Armin Kuster 2018-11-15 21:49:56 UTC
Can you still answer the question. Should an "Assertion Error" cause the build to fail?
Comment 7 Richard Purdie 2018-11-16 11:52:32 UTC
Yes, if gpg is missing the test should fail
Comment 9 Armin Kuster 2019-01-17 14:53:58 UTC
patch fixed issue
Comment 10 Armin Kuster 2019-01-17 14:54:11 UTC
.