Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Changqing Li <changqing.li@windriver.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH V3] dnf.py: installroot support usrmerge
Date: Wed, 4 Sep 2019 16:36:18 +0800	[thread overview]
Message-ID: <761df36a-5ea2-4b07-3e78-a0b5a4276908@windriver.com> (raw)
In-Reply-To: <413ea6ab6c76a8a532b7d28303b54fe61f12cd99.camel@linuxfoundation.org>


On 9/4/19 4:15 PM, Richard Purdie wrote:
> On Wed, 2019-09-04 at 16:04 +0800, Changqing Li wrote:
>> Ping
>> Test with/without  usrmege feature passed.
>> With usrmerge:
>> NOTE: test_dnf_installroot (dnf.DnfRepoTest)
>> DEBUG: Checking if 'DISTRO_FEATURES' value contains 'usrmerge' to
>> skip the test
>> NOTE:  ... skipped 'Test run when not enable usrmerge'
>> Test run when not enable usrmerge
>> NOTE: test_dnf_installroot_usrmerge (dnf.DnfRepoTest)
>> DEBUG: Checking if 'DISTRO_FEATURES' value contains 'usrmerge' to run
>> the test
>> DEBUG: [Running]$ ssh -l root -o UserKnownHostsFile=/dev/null -o
>> StrictHostKeyChecking=no -o LogLevel=ERROR 192.168.7.16 export
>> PATH=/usr/sbin:/sbin:/usr/bin:/bin; mkdir -p
>> /home/root/chroot/test/etc
>> ....
>>
>> Without usrmerge:
>> NOTE: test_dnf_installroot (dnf.DnfRepoTest)
>> DEBUG: Checking if 'DISTRO_FEATURES' value contains 'usrmerge' to
>> skip the test
>> DEBUG: [Running]$ ssh -l root -o UserKnownHostsFile=/dev/null -o
>> StrictHostKeyChecking=no -o LogLevel=ERROR 192.168.7.10 export
>> PATH=/usr/sbin:/sbin:/usr/bin:/bin; mkdir -p
>> /home/root/chroot/test/etc
>> DEBUG: time: 1567404974.8490767, endtime: 1567406474.8424258
>> DEBUG: [Command returned '0' after 0.13 seconds]
>> DEBUG: Command: mkdir -p /home/root/chroot/test/etc
>> Output:
>> ...
>> NOTE:  ... ok
>> NOTE: test_dnf_installroot_usrmerge (dnf.DnfRepoTest)
>> DEBUG: Checking if 'DISTRO_FEATURES' value contains 'usrmerge' to run
>> the test
>> NOTE:  ... skipped 'Test run when enable usrmege'
>> Test run when enable usrmege
> In a previous version of this patch, it introduced a failure in the
> parselogs test as an error was generated into the logs. I haven't
> tested the new version of the patch, was that issue addressed?
>
> Cheers,
>
> Richard

I didn't met failure in test_parselog during test,  the whole testimage 
is passed.

Could you help to send me the link of the failure test if the new 
version still

met test_parselog failure? Thanks.

>
>
>
-- 
BRs

Sandy(Li Changqing)



  reply	other threads:[~2019-09-04  8:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-03  4:46 [PATCH V3] dnf.py: installroot support usrmerge changqing.li
2019-09-04  8:04 ` Changqing Li
2019-09-04  8:15   ` Richard Purdie
2019-09-04  8:36     ` Changqing Li [this message]
2019-09-05 18:25       ` Randy MacLeod
2019-09-06 21:50         ` richard.purdie

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=761df36a-5ea2-4b07-3e78-a0b5a4276908@windriver.com \
    --to=changqing.li@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.org \
    /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