+cc RP

The default behavior is to look for a bitbake command, which fails and produces a confusing output of [-1:]. [YOCTO #14208] Signed-off-by: Yi Fan Yu <yifan.yu@...> --- scripts/utils.py | 3 +

This is the default oe-core MACHINE value. Prevent error-reporting tool to report simply False. It was seen in check-layer where the MACHINE wasn't specified. [YOCTO #14208] Signed-off-by: Yi Fan Yu <

LGTM, solves my bug and my issue with the old timeout behaviour. I tested glib-2.0 with the extra debugging output. It works. Also doesn't timeout. --- I looked at https://linux.die.net/man/2/alarm I

I don't see a huge amount of use of `timeout-ptest` since many tests I looked at have their own timeout mechanism built-in to individual tests (OR we have patched in... ex: valgrind). This has the adv

TY for the patches. This would change its behaviour to timeout exactly at X seconds. New behaviour: if test exceeds X seconds, gets killed. Old behaviour: if test exceeds X seconds with no output, get

would need to add that to `requirements.txt` i tested it quickly and it gave me bleach not found would it make more sense to bleach/sanitize the raw data before it got parsed into a json object so eve

RP, if you want to get this merged too that would be great. yifan

mostly changed the way to access request.GET also tested on python2.7 to be backward compatible Signed-off-by: Yi Fan Yu <yifan.yu@...> --- Post/parser.py | 2 +- Post/views.py | 14 +++++++--

if `MACHINE` is set to False (in a selftest build), contains_tags should skip that field instead of searching for the character '<'. [YOCTO #14208] Signed-off-by: Yi Fan Yu <yifan.yu@...> --

new here, pointing out of the obvious? website https://layers.openembedded.org/

#yocto

i didn't spend too much time getting the patch to look nice. It is just a proposal because this seems to be the root cause of a seemingly ... unrelated bug. https://bugzilla.yoctoproject.org/show_bug.

If the output of the testing script is very large, the fwrite called by the parent in wait_child would start blocking. That would slow down the parent speed in clearing the pipe buffer. This is an iss

Hi, Is there a fix/patch to chromium-x11 (meta-browser) failing to build `yocto_native/brotli`. This happens on Centos 8 where libatomic is not necessarily present on the host. as far as i know, libat