[PATCH] core-image-sato-sdk-ptest: use 3G of RAM

[PATCH] core-image-sato-sdk-ptest: use 3G of RAM

[Changqing Li]

[YOCTO #14164]

Some ptest cases, for example, libinput ptest intermittent failure on
arm64, this should caused by OOM Killer.

Signed-off-by: Changqing Li <changqing.li@windriver.com>
---
 meta/recipes-sato/images/core-image-sato-sdk-ptest.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-sato/images/core-image-sato-sdk-ptest.bb b/meta/recipes-sato/images/core-image-sato-sdk-ptest.bb
index bf749acd79..b3ce859d76 100644
--- a/meta/recipes-sato/images/core-image-sato-sdk-ptest.bb
+++ b/meta/recipes-sato/images/core-image-sato-sdk-ptest.bb
@@ -17,7 +17,7 @@ IMAGE_ROOTFS_EXTRA_SPACE = "1124288"
 
 # ptests need more memory than standard to avoid the OOM killer
 # also lttng-tools needs /tmp that has at least 1G
-QB_MEM = "-m 2048"
+QB_MEM = "-m 3072"
 
 # Sadly at the moment the full set of ptests is not robust enough and sporadically fails in random places
 PTEST_EXPECT_FAILURE = "1"
-- 
2.17.1

Re: [OE-core] [PATCH] core-image-sato-sdk-ptest: use 3G of RAM

[Richard Purdie]

On Tue, 2021-01-26 at 13:36 +0800, Changqing Li wrote:
> [YOCTO #14164]
> 
> Some ptest cases, for example, libinput ptest intermittent failure on
> arm64, this should caused by OOM Killer.
> 
> Signed-off-by: Changqing Li <changqing.li@windriver.com>
> ---
>  meta/recipes-sato/images/core-image-sato-sdk-ptest.bb | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/meta/recipes-sato/images/core-image-sato-sdk-ptest.bb b/meta/recipes-sato/images/core-image-sato-sdk-ptest.bb
> index bf749acd79..b3ce859d76 100644
> --- a/meta/recipes-sato/images/core-image-sato-sdk-ptest.bb
> +++ b/meta/recipes-sato/images/core-image-sato-sdk-ptest.bb
> @@ -17,7 +17,7 @@ IMAGE_ROOTFS_EXTRA_SPACE = "1124288"
>  
> 
> 
> 
>  # ptests need more memory than standard to avoid the OOM killer
>  # also lttng-tools needs /tmp that has at least 1G
> -QB_MEM = "-m 2048"
> +QB_MEM = "-m 3072"
> 

What is libinput doing that needs 3GB of memory? Is this because its
loading a whole graphics stack for testing or something? It seems odd
that we need that much memory for input drivers!

Cheers,

Richard