Hello All,
This is the full report for yocto-3.1.10.rc1:
https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults
=== Summary
No high milestone defects.
One issue observed in this release:
Bug 14488 - AB-INT PTEST: tcl socket.test inter
Hello all,
This is the full report for yocto-3.3.2.rc2:
https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults
=== Summary
No high milestone defects.
One existing issue observed in this release:
Bug 14388 - AB-INT PTEST: valgrind fail
Hello all,
This is the full report for yocto-3.4_M2.rc1:
https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults
=== Summary
No high milestone defects.
2 new issue found
BUG id:14489 - [3.4 M2 beaglebone] There are some warnings for
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
Hello all,
This is the full report for yocto-3.1.9.rc1:
https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults
=== Summary
No high milestone defects.
No new issue found.
Thanks,
Sangeeta
> -Original Message-
> From: qa-build-no
Hi all,
This is the full report for yocto-3.4_M1.rc1:
https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults
=== Summary
No high milestone defects.
new issue found
BUG id:14434 - [3.4 M1] dmesg: proc: Bad value for 'hidepid' with poky
Hi all,
Intel and WR YP QA is planning for QA execution for YP build yocto-3.4_M1.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
Hi all,
This is the full report for yocto-3.1.8.rc1:
https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults
=== Summary
No high milestone defects.
1 new issue found:
BUG id:14414 - [QA 3.1.8 RC1] failure in ptest :
strace.printstrn-umo
Hi all,
Intel and WR YP QA is planning for QA execution for YP build yocto-3.1.8.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 7
Hello All,
This is the full report for yocto-3.3.1.rc1:
https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults
=== Summary
No high milestone defects.
No new issue found.
Thanks,
Sangeeta
> -Original Message-
> From: qa-build-n
Hello All,
This is the full report for yocto-3.2.4.rc1:
https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults
=== Summary
No high milestone defects.
One new issue found:
Bug 14392 - [QA 3.2.4 RC1] failure in ptest : ptestresult.lttng-t
Hi all,
Intel and WR YP QA is planning for QA execution for YP build yocto-3.2.4.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 7
Hi All,
This is the full report for yocto-3.1.7.rc1:
https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults
=== Summary
No high milestone defects.
no new issue found
Thanks,
Sangeeta
> -Original Message-
> From: qa-build-notif
Hi all,
Intel and WR YP QA is planning for QA execution for YP build yocto-3.1.7.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 7
Hello All,
This is the full report for yocto-3.3.rc2:
https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults
=== Summary
No high milestone defects.
No new issue found.
Thanks,
Sangeeta
> -Original Message-
> From: yo...@list
Hello All,
This is the full report for yocto-3.2.3.rc1:
https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults
=== Summary
No high milestone defects.
No new issues found
Thanks,
Sangeeta
> -Original Message-
> From: qa-build-
Hi all,
Intel and WR YP QA is planning for QA execution for YP build yocto-3.2.3.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 7
Hi All,
This is the full report for yocto-3.3_M3.rc2:
https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults
=== Summary
No high milestone defects.
No new issue found:
Bugs verified:
BUG id:14306 - [3.3 M3 rc1] beaglebone poky-alt wic
Hi all,
Intel and WR YP QA is planning for QA execution for YP build yocto-3.3_M3.rc2.
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
Hi All,
This is the full report for yocto-3.3_M3.rc1:
https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults
=== Summary
No high milestone defects.
new issue found:
BUG id:14306 - [3.3 M3 rc1] beaglebone poky-alt wic image can not boo
Hi all,
Intel and WR YP QA is planning for QA execution for YP build yocto-3.3_M3.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
From: sangeeta jain
This update will ensure that recipes are not including time stamps by creating
an
image with modified system time. It uses libfaketime recipe to fake system
time to advance by 34308122 seconds
Signed-off-by: sangeeta jain
---
meta/lib/oeqa/selftest/cases/reproducible.py
From: sangeeta jain
libfaketime intercepts various system calls that programs use to retrieve the
current date and time. It then reports modified (faked) dates and times (as
specified the user) to these programs. It can modify the system time a
program sees without having to change the time
From: sangeeta jain
libfaketime intercepts various system calls that programs use to retrieve the
current date and time. It then reports modified (faked) dates and times (as
specified the user) to these programs. It can modify the system time a
program sees without having to change the time
From: sangeeta jain
This update will ensure that recipes are not including time stamps by creating
an
image with modified system time. It uses libfaketime recipe to fake system
time to advance by 34308122 seconds.
Signed-off-by: sangeeta jain
---
meta/lib/oeqa/selftest/cases/reproducible.py
Hi all,
This is the full report for yocto-3.1.6.rc1:
https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults
=== Summary
No high milestone defects.
no new issue found
Thanks,
Sangeeta
> -Original Message-
> From: qa-build-notif
Hi all,
Intel and WR YP QA is planning for QA execution for YP build yocto-3.1.6.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 7
Hi all,
This is the full report for yocto-3.2.2.rc1:
https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults
=== Summary
No high milestone defects.
No new issues found
Thanks,
Sangeeta
> -Original Message-
> From: yo...@lists
Hi all,
Intel and WR YP QA is planning for QA execution for YP build yocto-3.2.2.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 7
Hi All,
This is the full report for yocto-3.3_M2.rc1:
https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults
=== Summary
No high milestone defects.
new issue found
BUG id:14203 - [QA 3.3 M2 RC1] failure in ptest :
gstreamer1.0.gstre
Hi all,
Intel and WR YP QA is planning for QA execution for YP build yocto-3.3_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
Hi All,
This is the full report for yocto-3.1.5.rc1:
https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults
=== Summary
No high milestone defects.
no new issue found
Thanks,
Sangeeta
> -Original Message-
> From: Pokybuild Us
Hi all,
Intel and WR YP QA is planning for QA execution for YP build yocto-3.1.5.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 7
Hello All,
This is the full report for yocto-3.3_M1.rc2:
https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults
=== Summary
No new defects are found.
No high milestone defects.
Bugs verified:
BUG id:13997 - [QA 3.2 M2 RC1] failure
Hi all,
Intel and WR YP QA is planning for QA execution for YP build yocto-3.3_M1.rc2.
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
Hello All,
This is the full report for yocto-3.2.1.rc2:
https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults
=== Summary
No high milestone defects.
No new issues found
Existing bugs observed in this release:
BUG id:14051 - [Q
Hi all,
Intel and WR YP QA is planning for QA execution for YP build yocto-3.2.1.rc2.
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 7
From: sangeeta jain
updated command used for cross compilation to include ${CONFIGUREOPTS}
to ensure right arguments are passed for cross compiling on any host.
Signed-off-by: sangeeta jain
---
meta/lib/oeqa/manual/oe-core.json | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Hello all,
This is the full report for yocto-3.1.4.rc1:
https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults
=== Summary
No high milestone defects.
new issue found
BUG id:14138 - [QA 3.1.4 RC1] failure in oe-core manual test:
tes
Hi all,
Intel and WR YP QA is planning for QA execution for YP build yocto-3.1.4.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 7
Hello all,
This is the full report for yocto-3.1.3.rc1:
https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults
=== Summary
No high milestone defects.
No new defects are found in this cycle.
perl ptest failed (BUG id:14071)
=== B
Hi all,
Intel and WR YP QA is planning for QA execution for YP build yocto-3.2_M3.rc2.
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 7
Hello all,
This is the full report for yocto-3.2_M3.rc1:
https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults
=== Summary
Beaglebone can not boot up, hence all beaglebone test case are blocked in this
release.
No high milestone defec
Hello all,
This is the full report for yocto-3.0.4.rc1:
https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults
=== Summary
No high milestone defects.
No new defects are found in this cycle.
Thanks,
Sangeeta
> -Original Message-
Thanks,
sangeeta
> -Original Message-
> From: akuster808
> Sent: Thursday, 30 July, 2020 7:51 AM
> To: Jain, Sangeeta ; yo...@lists.yoctoproject.org;
> openembedded-core
> Cc: ota...@ossystems.com.br; yi.z...@windriver.com; Sangal, Apoorv
> ; Yeoh, Ee Peng ; Chan,
> Aaron Chun Yew ;
> ri
Hi All,
This is the QA report for yocto-3.1.2.rc1:
https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults
=== Summary
No high milestone defects.
No new defects are found in this cycle.
Thanks,
Sangeeta
> -Original Message-
>
From: sangeeta jain
Allow the creation of test case configuration file based on user inputs.
Where this testcase configuration file will be used by the the manual
execution to run selected test cases for a module rather than compulsory
run all test cases in manual json file.
Signed-off-by
From: sangeeta jain
Current manualexecution required user to exceute all test cases defined inside
a "modulename.json" file in oeqa/manual
There are cases when all test cases all not required to run for a module on
specific DUT.
Enable manualexecution to have the optional featur
From: sangeeta jain
All test id (eg. @alias) inside manual testcase file shall follow the same test
id
naming convention from oeqa automated tests (eg. selftest, runtime, sdk, etc),
where
the test id consists of ...
Furthermore,
there shall be only 1 unique test_module per each manual
From: sangeeta jain
Two changes made in oeqa/manual/compliance-test.json:
1. All test id (eg. @alias) inside manual testcase file shall follow the same
test id
naming convention from oeqa automated tests (eg. selftest, runtime, sdk, etc),
where
the test id consists of ...
Furthermore,
there
From: sangeeta jain
Two changes made in oeqa/manual/bsp-hw.json:
1. All test id (eg. @alias) inside manual testcase file shall follow the same
test id naming
convention from oeqa automated tests (eg. selftest, runtime, sdk, etc), where
the
test id consists of ... Furthermore,
there shall be
From: sangeeta jain
Manual test step for SDK is updated. Previously toolchain was
"poky-glibc-x86_64-core-image-sato-sdk-toolchain-.sh"
But toochain for core-image-sato-sdk is not available in releases after 2.1,
hence changed it to
"poky-glibc-x86_64-core-image-sato--toolc
52 matches
Mail list logo
