All of lore.kernel.org
 help / color / mirror / Atom feed
From: richard.purdie@linuxfoundation.org
To: "Mittal, Anuj" <anuj.mittal@intel.com>,
	"Kai.Kang@windriver.com" <Kai.Kang@windriver.com>,
	"Burton, Ross" <ross.burton@intel.com>
Cc: "poky@yoctoproject.org" <poky@yoctoproject.org>,
	"openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/2] defaultsetup.conf: enable select init manager
Date: Tue, 23 Jul 2019 20:30:43 +0100	[thread overview]
Message-ID: <71422bd44cac604f8a076b30a5d353669cc0b314.camel@linuxfoundation.org> (raw)
In-Reply-To: <73fdb42fa63f84e7ed6ec52a183bff73edc4272b.camel@intel.com>

On Mon, 2019-07-22 at 23:26 +0000, Mittal, Anuj wrote:
> On Mon, 2019-07-22 at 09:37 +0800, Kang Kai wrote:
> > I just run oe-selftest -a with this patch after you updated the
> > patch
> > in 
> > oe-core. But I met some (>15) errors
> > 
> > ERROR: Unable to start bitbake server (None)
> > 
> > But I think it should not be related with init manager changes and
> > will 
> > change a build machine to test.
> > Do you have test it again in autobuilder and any failure found?
> > Thanks.
> 
> Not sure if these have been reported but there are some failures in
> runtime tests which look related to this change:
> 
> https://autobuilder.yoctoproject.org/typhoon/#/builders/38/builds/855/steps/8/logs/step1c
> 
> https://autobuilder.yoctoproject.org/typhoon/#/builders/50/builds/852/steps/8/logs/step1c
> 
> https://autobuilder.yoctoproject.org/typhoon/#/builders/76/builds/856/steps/8/logs/step2c

I did a back to back build comparision with and without the init system
change.

Basically every failure in:

https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/297

seems to be due to the init system default change so we have some
issues in there to resolve before we can change the default.

Cheers,

Richard



WARNING: multiple messages have this Message-ID (diff)
From: richard.purdie@linuxfoundation.org
To: "Mittal, Anuj" <anuj.mittal@intel.com>,
	"Kai.Kang@windriver.com" <Kai.Kang@windriver.com>,
	"Burton, Ross" <ross.burton@intel.com>
Cc: "poky@yoctoproject.org" <poky@yoctoproject.org>,
	"openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [oe-core][PATCH 1/2] defaultsetup.conf: enable select init manager
Date: Tue, 23 Jul 2019 20:30:43 +0100	[thread overview]
Message-ID: <71422bd44cac604f8a076b30a5d353669cc0b314.camel@linuxfoundation.org> (raw)
In-Reply-To: <73fdb42fa63f84e7ed6ec52a183bff73edc4272b.camel@intel.com>

On Mon, 2019-07-22 at 23:26 +0000, Mittal, Anuj wrote:
> On Mon, 2019-07-22 at 09:37 +0800, Kang Kai wrote:
> > I just run oe-selftest -a with this patch after you updated the
> > patch
> > in 
> > oe-core. But I met some (>15) errors
> > 
> > ERROR: Unable to start bitbake server (None)
> > 
> > But I think it should not be related with init manager changes and
> > will 
> > change a build machine to test.
> > Do you have test it again in autobuilder and any failure found?
> > Thanks.
> 
> Not sure if these have been reported but there are some failures in
> runtime tests which look related to this change:
> 
> https://autobuilder.yoctoproject.org/typhoon/#/builders/38/builds/855/steps/8/logs/step1c
> 
> https://autobuilder.yoctoproject.org/typhoon/#/builders/50/builds/852/steps/8/logs/step1c
> 
> https://autobuilder.yoctoproject.org/typhoon/#/builders/76/builds/856/steps/8/logs/step2c

I did a back to back build comparision with and without the init system
change.

Basically every failure in:

https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/297

seems to be due to the init system default change so we have some
issues in there to resolve before we can change the default.

Cheers,

Richard



  reply	other threads:[~2019-07-23 19:30 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-04 13:45 [PATCH v7 0/2] Make systemd as default init manager kai.kang
2019-07-04 13:45 ` [PATCH 1/2] defaultsetup.conf: enable select " kai.kang
2019-07-04 13:45   ` [oe-core][PATCH " kai.kang
2019-07-06  9:53   ` [PATCH " Adrian Bunk
2019-07-06  9:53     ` [OE-core] [oe-core][PATCH " Adrian Bunk
2019-07-06 12:08     ` [PATCH " Adrian Bunk
2019-07-06 12:08       ` [OE-core] [oe-core][PATCH " Adrian Bunk
2019-07-06 12:31     ` [PATCH " richard.purdie
2019-07-06 12:31       ` [OE-core] [oe-core][PATCH " richard.purdie
2019-07-08  9:28       ` [PATCH " Kang Kai
2019-07-08  9:28         ` [OE-core] [oe-core][PATCH " Kang Kai
2019-07-08 10:01       ` [PATCH " ChenQi
2019-07-08 10:01         ` [OE-core] [oe-core][PATCH " ChenQi
2019-07-08  2:01     ` [PATCH " Kang Kai
2019-07-08  2:01       ` [OE-core] [oe-core][PATCH " Kang Kai
2019-07-08  2:13       ` [PATCH " Kang Kai
2019-07-08  2:13         ` [OE-core] [oe-core][PATCH " Kang Kai
2019-07-19 21:35   ` [PATCH " Burton, Ross
2019-07-19 21:35     ` [OE-core] [oe-core][PATCH " Burton, Ross
2019-07-19 22:28     ` [PATCH " richard.purdie
2019-07-19 22:28       ` [OE-core] [oe-core][PATCH " richard.purdie
2019-07-22  1:37       ` [PATCH " Kang Kai
2019-07-22  1:37         ` [OE-core] [oe-core][PATCH " Kang Kai
2019-07-22 23:26         ` [PATCH " Mittal, Anuj
2019-07-22 23:26           ` [OE-core] [oe-core][PATCH " Mittal, Anuj
2019-07-23 19:30           ` richard.purdie [this message]
2019-07-23 19:30             ` richard.purdie
2019-07-25 11:10             ` [PATCH " Kang Kai
2019-07-25 11:10               ` [OE-core] [oe-core][PATCH " Kang Kai
2019-07-04 13:45 ` [meta-poky][PATCH 2/2] poky.conf: make systemd as default " kai.kang
2019-07-04 22:34   ` richard.purdie
2019-07-04 15:00 ` ✗ patchtest: failure for Make " Patchwork

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=71422bd44cac604f8a076b30a5d353669cc0b314.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=Kai.Kang@windriver.com \
    --cc=anuj.mittal@intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=poky@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.