Hi all,
Intel and WR YP QA is planning for QA execution for YP build yocto-3.4_M2.rc1.
We are planning to execute following tests for this cycle:
OEQA-manual tests for following module:
1. OE-Core
2. BSP-hw
Runtime auto test for following platforms:
1. MinnowTurbot 32-bit
2. Coffee Lake
3. NUC
In message: [linux-yocto][yocto-kernel-cache][yocto-5.10][PATCH 0/7] Enable
some features on Intel Elkhart Lake CRB
on 21/07/2021 Yongxin Liu wrote:
> Hi Bruce,
>
> Could you help to merge those 7 patches to yocto-kernel-cache, branch
> yocto-5.10?
> The first 3 patches are cherry-picked from
merged.
Bruce
In message: [linux-yocto][yocto-kernel-cache yocto-5.10][PATCH 0/2] nxp-imx8:
Enable imx8 USB3 and WM8960 feature related configuration
on 21/07/2021 Xiaolei Wang wrote:
> This review mainly enable imx8 USB3 and WM8960 feature related configuration
>
> Xiaolei Wang (2):
>
AFAIK, passing arguments from a python function to a shell function is
not allowed
On 7/21/21 10:45 AM, Bel Hadj Salem Talel wrote:
Hi All,
I have this example that can call a shell function from a python task:
*shell_function(){*
* bbwarn "This is a shell function, arg1 = $1"*
*}*
Hi Armin
Using the meta-integrety layer and I'm able to deploy the image but I
don't have the attribute insde the ext4 and wic image I create.
Do you know what step are missing?
Michael
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#54185):
Hi All,
I have this example that can call a shell function from a python task:
*shell_function(){*
*bbwarn "This is a shell function, arg1 = $1"*
*}*
*python do_something(){*
*bb.build.exec_func('shell_function', d)*
*}*
How to pass arguments to the shell function ?
I tried this : "
Yocto Technical Team Minutes, Engineering Sync, for July 20, 2021
archive:
https://docs.google.com/document/d/1ly8nyhO14kDNnFcW2QskANXW3ZT7QwKC5wWVDg9dDH4/edit
== disclaimer ==
Best efforts are made to ensure the below is accurate and valid. However,
errors sometimes happen. If any errors or
Up till now ptest-runner2 returns number of failed tests with its
exit status code. Such use case is not recommended [1] and may cause
issues when there are more than 256 tests to be executed.
To alleviate this issue the number of total tests with number of failed
ones is printed before exit. To
From: Adrian Freihofer
Try to make memory management more robust by assigning always NULL to
struct ptest_list pointers. It's a refactoring which probably improves
the code but does not fix a concrete bug.
Signed-off-by: Adrian Freihofer
---
main.c | 9 +
ptest_list.c
From: Adrian Freihofer
Removes the following warnings thrown by
make && valgrind -s --leak-check=full ./ptest-runner -d tests/data2
==4154390== Invalid write of size 8
==4154390==at 0x40360D: run_child (utils.c:357)
==4154390==by 0x403C5B: run_ptests (utils.c:534)
==4154390==by
From: Adrian Freihofer
make && valgrind -s --leak-check=full ./ptest-runner -d tests/data2
==4154029== HEAP SUMMARY:
==4154029== in use at exit: 20 bytes in 2 blocks
==4154029== total heap usage: 45 allocs, 43 frees, 42,909 bytes allocated
==4154029==
==4154029== 20 (8 direct, 12
From: Adrian Freihofer
Signed-off-by: Adrian Freihofer
---
.gitignore | 3 +++
1 file changed, 3 insertions(+)
create mode 100644 .gitignore
diff --git a/.gitignore b/.gitignore
new file mode 100644
index 000..ef07e6a
--- /dev/null
+++ b/.gitignore
@@ -0,0 +1,3 @@
+*.o
+ptest-runner
This patch series provides some memory management fixes and corrected
return code handling for ptest-runner2.
Adrian Freihofer (4):
git: Extend the gitignore
mem: Fix memleak for ptest_opts
mem: Simplify memory management
mem: Refactor ptest_list cleanup
Lukasz Majewski (1):
main: Do
A build flagged for QA (yocto-3.4_M2.rc1) was completed on the autobuilder and
is available at:
https://autobuilder.yocto.io/pub/releases/yocto-3.4_M2.rc1
Build hash information:
bitbake: 13e2855bff6a6ead6dbd33c5be4b988aafcd4afa
meta-arm: 9efa3b5683a5dd7ebbf63ff31b889ed589ff7a9a
14 matches
Mail list logo
