Nope. This is an odd one. Are you sure there isn't a problem with the
setup itself? In step2c, I see:
> ERROR: core-image-sato-1.0-r0 do_testsdk: The toolchain
/home/pokybuild/yocto-worker/qemuarm-oecore/build/build/tmp-glibc/deploy/sdk/oecore-i686-armv7vet2hf-neon-toolchain-nodistro.0.sh
is not built. Build it before running the tests: 'bitbake <image> -c
populate_sdk' .
On 13.01.20 13:18, Richard Purdie wrote:
On Sun, 2020-01-12 at 14:59 +0100, Carlos Rafael Giani wrote:
* gstreamer1.0-plugins-common.inc
The old gstreamer1.0-plugins.inc file, adapted for meson
* gstreamer1.0-plugins-packaging.inc
The old gst-plugins-package.inc file, adapted for meson
* gstreamer1.0-ptest.inc
Common code for meson based PTest support; autogenerates the run-ptest
file and is designed to use the gnome-desktop-testing suite runner
(which is why the .inc files inherits from ptest-gnome)
Signed-off-by: Carlos Rafael Giani <[email protected]>
---
.../gstreamer/gstreamer1.0-plugins-common.inc | 47 +++++++++++++
.../gstreamer1.0-plugins-packaging.inc | 70 +++++++++++++++++++
.../gstreamer/gstreamer1.0-ptest.inc | 21 ++++++
3 files changed, 138 insertions(+)
create mode 100644
meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-common.inc
create mode 100644
meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-packaging.inc
create mode 100644 meta/recipes-multimedia/gstreamer/gstreamer1.0-ptest.inc
Thanks for this, I know its not an easy patch set to sort out!
I ran it on the autobuilder for testing since there was bandwidth
available and there was one issue:
https://autobuilder.yoctoproject.org/typhoon/#/builders/47/builds/1455
which was in a plain OE-Core + bitbake build (no poky, so nodistro).
Any idea what is wrong there?
Cheers,
Richard
--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core
