From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: Jose Perez Carranza <jose.perez.carranza@linux.intel.com>,
"Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH v3] runtime/dnf: Add new dnf test cases
Date: Thu, 8 Jun 2017 19:35:05 +0300 [thread overview]
Message-ID: <f3d6469c-b0a8-6f75-7c02-e8afd0cf04bd@linux.intel.com> (raw)
In-Reply-To: <e1d6c111-bd9d-af76-ae44-d6921c723ba6@linux.intel.com>
On 06/07/2017 08:31 PM, Jose Perez Carranza wrote:
> When I tried this test image was built without using states hence
> "busybox*.rpm" and "curl*.rpm"where present under
> "tmp/deploy/rpm/core2_64" hence the repo i taking tha packages form
> there to add them to repo and used on the image, but when using sstates
> those packages are not being built so are not present on local build
> directory. is there any way to force those packages to be built to have
> them available on tmp/deploy/rpm/core2_64?
At least one of the failures has nothing to do with sstate or repositories:
File
"/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-x32/build/meta/lib/oeqa/runtime/cases/dnf.py",
line 136, in test_dnf_exclude
if self.dnf('list curl %s' % excludepkg ,0):
File
"/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-x32/build/meta/lib/oeqa/runtime/cases/dnf.py",
line 18, in dnf
self.assertEqual(status, expected, message)
AssertionError: 1 != 0 : dnf list curl curl-dev
Error: No matching Packages to list
That line is asking if curl package is installed on the image, and, in
core-image-sato's case it isn't, and so failure occurs. The repositories
are not even accessed.
I haven't been able to reproduce the installroot failure, works fine here.
Alex
next prev parent reply other threads:[~2017-06-08 16:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-10 19:38 [PATCH] runtime/dnf: Add new dnf test cases jose.perez.carranza
2017-05-10 19:52 ` Alexander Kanavin
2017-05-11 17:33 ` [PATCH v2] " jose.perez.carranza
2017-05-11 18:56 ` Alexander Kanavin
2017-05-11 19:21 ` Jose Perez Carranza
2017-05-15 13:50 ` [PATCH v3] " jose.perez.carranza
2017-06-07 10:21 ` Burton, Ross
2017-06-07 17:31 ` Jose Perez Carranza
2017-06-08 11:31 ` Alexander Kanavin
2017-06-08 12:49 ` Jose Perez Carranza
2017-06-08 12:49 ` Alexander Kanavin
2017-06-08 13:11 ` Jose Perez Carranza
2017-06-08 16:35 ` Alexander Kanavin [this message]
2017-06-09 9:22 ` Alexander Kanavin
2017-06-09 12:54 ` Jose Perez Carranza
2017-06-13 19:56 ` [PATCH v4] " jose.perez.carranza
2017-06-14 12:00 ` Alexander Kanavin
2017-06-14 12:32 ` Jose Perez Carranza
2017-11-30 16:23 ` [PATCH v5] " jose.perez.carranza
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f3d6469c-b0a8-6f75-7c02-e8afd0cf04bd@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=jose.perez.carranza@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox