MIRRORS/poky
1
0
Fork 0
mirror of git://git.yoctoproject.org/poky.git synced 2025-07-19 21:09:03 +02:00
Code Issues Actions Packages Projects Releases Wiki Activity
52,224 Commits 39 Branches 594 Tags 250 MiB
Python 53.7%
BitBake 12.7%
HTML 10.9%
Roff 6.2%
Pawn 3.6%
Other 12.3%
fcf55f58ae
Go to file
Richard Purdie fcf55f58ae oeqa/runtime/ptest: Inject results+logs into stored json results file 
This allows the ptest results from ptest-runner, run in an image to be
transferred over to the resulting json results output.

Each test is given a pass/skip/fail so individual results can be monitored
and the raw log output from the ptest-runner is also dumped into the
results json file as this means after the fact debugging becomes much easier.

Currently the log output is not split up per test but that would make a good
future enhancement.

I attempted to implement this as python subTests however it failed as the
output was too confusing, subTests don't support any kind of log
output handling, subTest successes aren't logged and it was making things
far more complex than they needed to be.

We mark ptest-runner as "EXPECTEDFAILURE" since its unlikely every ptest
will pass currently and we don't want that to fail the whole image test run.
Its assumed there would be later analysis of the json output to determine
regressions. We do have to change the test runner code so that
'unexpectedsuccess' is not a failure.

Also, the test names are manipuated to remove spaces and brackets with
"_" used as a replacement and any duplicate occurrences truncated.

(From OE-Core rev: a13e088942e2a3c3521e98954a394e61a15234e8)

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-11-07 23:08:55 +00:00
bitbake bitbake: bitbake-user-manual: Added hard-spacing to "_remove" example. 2018-10-31 21:40:36 +00:00
documentation ref-manual: Updates to variable wildcard support 2018-10-29 16:55:19 +00:00
meta oeqa/runtime/ptest: Inject results+logs into stored json results file 2018-11-07 23:08:55 +00:00
meta-poky poky.conf: Bump version for 2.6 thud release 2018-10-29 17:32:20 +00:00
meta-selftest meta-skeleton/meta-selftest: Update to thud 2018-09-25 23:15:49 +01:00
meta-skeleton meta-skeleton/meta-selftest: Update to thud 2018-09-25 23:15:49 +01:00
meta-yocto-bsp linux-yocto: update genericx86* SRCREV for 4.18 2018-10-20 22:40:51 +01:00
scripts udev-hwdb: fix postinstall scripts failures when multilib enabled 2018-10-25 14:53:44 +01:00
.gitignore gitignore: Ignore repo tool directory 2018-10-29 17:26:47 +00:00
.templateconf meta-yocto: Rename to meta-poky to better match its purpose 2016-02-28 11:31:17 +00:00
LICENSE Fix license notices for OE-Core 2014-01-02 12:58:54 +00:00
oe-init-build-env oe-init-build-env-memres: Drop it 2017-07-21 08:44:25 +01:00
README.hardware meta-yocto: Restructure and tidy up READMEs 2017-09-14 13:36:22 +01:00
README.LSB pax: remove the recipe 2018-02-24 10:31:45 +00:00
README.poky meta-yocto: Restructure and tidy up READMEs 2017-09-14 13:36:22 +01:00
README.qemu README.qemu: qemuppc64 is not supported 2017-10-16 23:54:31 +01:00

README.qemu 

QEMU Emulation Targets
======================

To simplify development, the build system supports building images to
work with the QEMU emulator in system emulation mode. Several architectures
are currently supported in 32 and 64 bit variants:

  * ARM (qemuarm + qemuarm64)
  * x86 (qemux86 + qemux86-64)
  * PowerPC (qemuppc only)
  * MIPS (qemumips + qemumips64)

Use of the QEMU images is covered in the Yocto Project Reference Manual.
The appropriate MACHINE variable value corresponding to the target is given
in brackets.