Khem Raj
0d23ebf994
test/test1.cf sets "reinitcheck 1s", added upstream only to exercise the seconds unit. A reinit check brings back every console that is down, including one taken down on purpose, so test #5, which expects the console that test #4 downed ("cd") to still be down, has about a second to attach and query it. On a loaded host, e.g. while testimage runs several VMs, it loses: FAIL: conserver #5 (diffs in test5.diff) -[`shell' -- console is down] conserver.log shows "[shell] automatic reinitialization" between the two tests. Reproduced with 2 failures in 20 runs in qemux86-64 with the host CPUs saturated; instrumenting group.c confirmed the reinit comes from ReUp(pGE, 2), the reinitcheck timer. Use "reinitcheck 60s" in the test config, so the seconds unit is still parsed but the check cannot fire during the ~10 s test run. 40 of 40 runs passed under the same load. Tested with meta-oe-image-ptest-conserver on qemux86-64 with yoe-musl-systemd-wayland. AI-Generated: Uses Claude Code Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
meta-oe
This layer depends on:
URI: git://github.com/openembedded/openembedded-core.git branch: master
luajit recipe requires host compiler to be able to generate 32bit code when target is 32bit e.g. arm, so ensure that $CC -m32 is functional on build host, if building this recipe, needed packages to fullfit this might have different names on different host distributions e.g. on archlinux based distributions install prerequisites like below
pacman -S lib32-gcc-libs lib32-glibc
Ubuntu sudo apt-get install gcc-multilib linux-libc-dev:i386
Send pull requests to openembedded-devel@lists.openembedded.org with '[meta-oe]' in the subject'
When sending single patches, please use something like: 'git send-email -M -1 --to openembedded-devel@lists.openembedded.org --subject-prefix="meta-oe][PATCH"'
You are encouraged to fork the mirror on GitHub https://github.com/openembedded/meta-openembedded to share your patches, this is preferred for patch sets consisting of more than one patch.
Note, it is discouraged to send patches via GitHub pull request system. Such patches get less attention from developers and can be mishandled or not reviewed properly. Please use emails instead. For exemple, you can use 'git request-pull' to generate an email referencing your git repository.
Other services like GitLab, repo.or.cz or self-hosted setups are of course accepted as well, 'git fetch ' works the same on all of them. We recommend GitHub because it is free, easy to use, has been proven to be reliable and has a really good web GUI.
Layer maintainer: Khem Raj raj.khem@gmail.com