From: richard.purdie@linuxfoundation.org
To: Randy MacLeod <randy.macleod@windriver.com>,
Changqing Li <changqing.li@windriver.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH V3] dnf.py: installroot support usrmerge
Date: Fri, 06 Sep 2019 22:50:55 +0100 [thread overview]
Message-ID: <24bfa19f1db61860978894ae958aec938bd91ee1.camel@linuxfoundation.org> (raw)
In-Reply-To: <c48b2c01-d4b1-c0cf-54b1-4c8a00af9ea1@windriver.com>
On Thu, 2019-09-05 at 14:25 -0400, Randy MacLeod wrote:
> On 9/4/19 4:36 AM, Changqing Li wrote:
> > 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.
>
> Sandy,
>
> Richard shouldn't have to do that since many people have such
> requests and
>
> if he helped everyone he would (and has in the past) spend/t too
> much
> time helping people.
>
> We should be able to setup the autobuilder locally to reproduce the
> problem.
>
>
> Also during the YP bug review call, someone suggested that you check
> if the
>
> dnf install tests are running in a deterministic order. If they are
> not,
> then that
>
> might explain why the AB sees the problem but you do not.
It wasn't clear if the issue was fixed in the revised patch or not so I
did include this in the last round of tests and those passed. I
therefore suspect whatever the issue was did get fixed in the v3.
Of course a different patch failed (mdadm) so I've replied about that
one separately (I've confirmed which patch it was manually, it did
reproduce).
Cheers,
Richard
prev parent reply other threads:[~2019-09-06 21:50 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
2019-09-05 18:25 ` Randy MacLeod
2019-09-06 21:50 ` richard.purdie [this message]
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=24bfa19f1db61860978894ae958aec938bd91ee1.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=changqing.li@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=randy.macleod@windriver.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