nitialization
to track detail for debugging in case test fail
Thanks,
Ee Peng
-Original Message-
From: Richard Purdie
Sent: Friday, April 17, 2020 10:24 PM
To: Yeoh, Ee Peng ;
openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] oeqa/runtime/weston: Enhance west
Hi Ee Peng,
On Fri, 2020-04-17 at 01:53 +, Yeoh, Ee Peng wrote:
> Hi Richard,
>
> After more testing, I realized that it will take different amount of
> time for each host machine to initialize new wayland compositor. I
> had added the logic to retry the checking of new wayland compositor
> t
.
Thank you very much!
Thanks,
Yeoh Ee Peng
-Original Message-
From: Richard Purdie
Sent: Friday, April 17, 2020 6:35 AM
To: Yeoh, Ee Peng ;
openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] oeqa/runtime/weston: Enhance weston tests
On Mon, 2020-04-13 at 16:49
On Mon, 2020-04-13 at 16:49 +0800, Yeoh Ee Peng wrote:
> Existing weston test available make sure that a process
> for weston-desktop-shell exist when image boot up.
>
> Enhance weston tests by:
> - execute weston-info to make sure weston interface(s)
>are initialized
> - execute weston and
Thanks, now one step closer to deprecating x11 :)
I'm thinking of rebasing all images used by autobuilder (e.g. -ptest, -sdk)
to be based off core-image-weston in 3.2 timeframe. The only sato image
would be core-image-sato itself.
Alex
On Mon, 13 Apr 2020 at 10:49, Yeoh Ee Peng wrote:
> Existi
Existing weston test available make sure that a process
for weston-desktop-shell exist when image boot up.
Enhance weston tests by:
- execute weston-info to make sure weston interface(s)
are initialized
- execute weston and make sure it can initialize a
new wayland compositor
[YOCTO# 1069
