I'm not aware of a specific list but two that come to mind are, (in meta-openembedded): $ rgrep PNBLACKLIST meta-*| wc -l 10 $ rgrep COMPATIBLE_HOST meta-*| wc -l 115 Maybe you can explain why you wan

#bitbake

Hi Armin, The community will fix bugs on HEAD just like before. It's a tag indicating where the branch was at GA time. There's no obligation for he maintainer do do anything in addition to what they w

How about: https://git.openembedded.org/meta-openembedded/commit/?id=71b546ed8595b14d29efc1e8b951f8c845ad10c4 ../Randy

It doesn't have a yocto-3.3 tag yet... Could you add one? ../Randy

Attendees: Richard, Randy To Do: ====== Data Collection: (Sakib) ------------------------ 1. run iostat if it exists: iostat -y -z -x 5 1 -y Omit first report with statistics since system boot, if dis

Adding Robert, Hongxu and Qi who are likely interested in this topic for future releases. Yes. It's always bothered me that the tag wasn't there and now that oe-core/bitbake/... have been doing it, it

Hi, I've CCed some of the maintainers of more widely used Yocto layers to get comments on about tagging. Please add in people who I may have missed. For a while now, oe-core has had a yocto-X.Y tag in

Cross-posting to yocto since this is of general interest. We (Wind River) already drop the x11 DF from some of our distros and we'd likely do the same for wayland and opengl so while this seems like t

Summary: Build: 20210420-1 had 23 triggers and isn't really worth analyzing. Stay tuned for what is hopefully better data with a higher timeout threshold. There is a nice looking pair of graph attache

With the previous interval of 10 seconds, there would be serveral times when the system was very busy and the script would not return before the next run was scheduled resulting in no measurement. In

Thanks for fixing the fall-out due to assumptions in other tests. Is the system back to normal and operational now? What was the impact of running the heartbeat and the dd test every 10 seconds on the

Richard, I think that the web server for: https://autobuilder.yocto.io/pub/non-release/ runs every 30 seconds via cron so if you are happy with this crude dd trigger once things have soaked in master-

We were using it for testing on the YP AB and thought it would be useful if at some point the monitoring was dropped from the default config. I think we can just add it later if needed. ../Randy

During today's Yocto technical call (1), we talked about approaches to limiting the system load and avoiding swap and/or OOM events. Here's what (little!) i recall from the discussion, 9 busy hours la

Thanks Jeremy. ../Randy

Is this layer alive? :) ../Randy

Khem was asking if anyone had seen a >30% difference in build time for qemuarm compared to other machines. I don't when building on my system: rmacleod@yow-rmacleod-lx3 b/c-i-m-x86 $ cat x86 real 43m2

Hello, It's a bit hard to know where to start without more information. Can you tell us what release, layers and hardware you are using? Are you able to reproduce the problem using runqemu ? Are you a

#yocto

glibc has mallinfo: https://stackoverflow.com/questions/8335402/how-to-find-how-much-memory-is-actually-used-up-by-a-malloc-call Yep, it's a beast! There are lighter memory debuggers such as the Addre

This is a rather vague question so you may not get a specific recommendation. Have you reviewed the list of html related recipes listed by the layer index: https://layers.openembedded.org/layerindex/b