[OE-core] [oe-core][PATCH 1/2] defaultsetup.conf: enable select init manager

[Kang Kai]

On 2019/7/24 上午3:30, richard.purdie at linuxfoundation.org wrote:
> 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


It fails with

$ bitbake core-image-sato-sdk -c testimage

RESULTS - systemd.SystemdBasicTests.test_systemd_failed: FAILED (0.56s)

It checks failed systemd services and got one:

UNIT              LOAD   ACTIVE SUB DESCRIPTION
● nfs-statd.service loaded failed failed NFS status monitor for NFSv2/3 
locking.


But when boot the qemu image or only run systemd testcases( with its 
dependenies), no such failure.
I doubt it may be affected by other test cases.

Regards,
Kai

>
> 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
>
>

-- 
Kai Kang