linux/poky.git/meta/recipes-core/glib-2.0/files/run-ptest, branch master

The poky repository master branch is no longer being updated.

2025-11-07T13:31:53+00:00

You can either: a) switch to individual clones of bitbake, openembedded-core, meta-yocto and yocto-docs b) use the new bitbake-setup You can find information about either approach in our documentation: https://docs.yoctoproject.org/ Note that "poky" the distro setting is still available in meta-yocto as before and we continue to use and maintain that. Long live Poky! Some further information on the background of this change can be found in: https://lists.openembedded.org/g/openembedded-architecture/message/2179 Signed-off-by: Richard Purdie

glib-2.0: double test runner timeout in run-ptest

2025-09-22T21:09:48+00:00

The gnome-desktop-testing-runner has a default timeout of 300s. With qemuriscv64, some tests in the glib-2.0 test suite (notably codegen.py.test and gi-compile-repository.py.test) can take a long time and exceed this timeout limit, resulting in intermittent test failures. To avoid this problem, double the timeout by passing '-t 600' to gnome-desktop-testing-runner. Although not a perfect comparison (I have to use 'taskset --cpu-list 0' to simulate loading in order to make the tests fail consistently on my local machine), it's worth noting that the timeout increase does result in a slightly longer test run. Here is an example of the duration when a failure happens under 'taskset --cpu-list 0 runqemu nographic snapshot':: |SUMMARY: total=298; passed=296; skipped=1; failed=1; user=606.7s; system=1388.3s; maxrss=170976 |FAIL: glib/codegen.py.test (Child process killed by signal 9) | |ERROR: Exit status is 2 |DURATION: 1368 |END: /usr/lib/glib-2.0/ptest |2025-09-18T19:04 |STOP: ptest-runner |TOTAL: 1 FAIL: 1 and a pass: |SUMMARY: total=298; passed=297; skipped=1; failed=0; user=682.2s; system=1295.0s; maxrss=170476 |+ userdel glib2-test |DURATION: 1402 |END: /usr/lib/glib-2.0/ptest |2025-09-18T17:23 |STOP: ptest-runner |TOTAL: 1 FAIL: 0 [YOCTO #15891] (From OE-Core rev: f634098ed6c5674d81028a7ea8e18a7a93a77fab) Signed-off-by: Trevor Gamblin Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie

glib/gobject-introspection: update 2.78.4 -> 2.80.0, 1.78.1 -> 1.80.0

2024-05-13T15:28:35+00:00

With these versions, which need to be updated in lockstep, upstream has relocated glib introspection data from g-i tree to glib tree and made its generation a part of the overall glib build. This creates a circular dependency, where g-i tools are linked with glib, but glib needs the tools to build its g-i data. (I don't know why the two source trees couldn't be simply merged into one, or g-i data for glib couldn't be generated inside g-i build against sysroot glib). Upstream is suggesting building glib twice, first without building g-i data, then building g-i and linking it with that version, then building the final glib, and that's what is being done here (via the new glib-initial recipe, which is sysroot-only, and is not pulled in via indirect dependencies either). Other glib changes: 0001-Do-not-write-bindir-into-pkg-config-files.patch restores writing bindir variable into glib.pc file (meson only writes it out if other variables depend on it, and this custom patch removes that dependency). 0001-girepository-introspection-correctly-install-.gir-fi.patch ensures correct installation of .gir into something else than $datadir (useful in multilib). Merge previous glib .bb into .inc, so that glib and glib-initial recipes could be cleanly separated with no duplication. Convert from gtk-doc to gi-docgen, and manpages from xmlto to docutils. (From OE-Core rev: 57c307536f67dcfb5d4a5488ca1e77a943ba1368) Signed-off-by: Alexander Kanavin Signed-off-by: Richard Purdie