When the log name contains a space, the generated URL is not correct. Thi= s later also breaks parsing in swatbot. This was triggered by "property changes" and the correct URL is indeed

Hi all, This is the full report for yocto-3.4_M1.rc1: https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults ======= Summary ======== No high milestone

From: Bruce Ashfield <bruce.ashfield@...> Updating linux-yocto/5.10 to the latest korg -stable release, and to match the qemu BSPs in oe-core Signed-off-by: Bruce Ashfield

The script goes over the raw logfile (for example, foo.txt) which consists of multiple top outputs and summarizes each top output and writes them to foo_summary.txt Some improvements that can be

Hello Alex, I was able to fix the iris driver issue with the following added to mesa.inc GALLIUMDRIVERS_append = "${@bb.utils.contains('PACKAGECONFIG', 'iris', ',iris', '', d)}" I will look into

[...] One quick question - the above assumes an x86 target machine using those two tunes.  Should that be wildcarded? Cheers, Richard

Hello Simon, I honestly don't know how Intel folks have overlooked this, but mesa in yocto not only does not enable iris, the mesa recipe does not even have an option to enable it. However, it should

Looks good Sakib, Can you show people what the typical output looks like? Is the raw top output still published? ../Randy -- # Randy MacLeod # Wind River Linux

Hi all, I'm having trouble figuring out how to fix my issues with the new intel NUC gen 11 (NUC11TNBi5). At the moment I'm testing with the following meta-layer poky (hardknott) meta-openembedded

Disables debuginfod when using MingGW. This feature brings in unbuildable dependencies and can't be used. Signed-off-by: Joshua Watt <JPEWhacker@...> ---

Hello All, I am tyro in yocto , I am having a strange issue where I am trying to build the recipe using devtool build <recipe> . It fails first time but builds second time. It flags an error

What I think happened is that glibc simply got better at linking, optimised the runtime bits to the fullest, and any benefits prelink may once have had aren't there anymore. Which is IMO fine - I am

The numbers certainly don't look convincing, thanks for running the tests. Mark and I did briefly talk yesterday and whilst Mark can/will speak up, the summary was "drop it". What makes me sad is

summarize_top_output.py is used to summarize the top output that is captured during autobuilder intermittent failures. Use the script to summarize the host top output and publish the summary that is

From: Kai Kang <kai.kang@...> The patch fix-ldblibdir.patch has been dropped when update sssd to 2.5.0. But it fails to start sssd without this patch. So add it back. Signed-off-by: Kai

Signed-off-by: Federico Pellegrin <fede@...> --- .../{aircrack-ng_1.3.bb => aircrack-ng_1.6.bb} | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) rename

Hi all, Intel and WR YP QA is planning for QA execution for YP build yocto-3.4_M1.rc1. We are planning to execute following tests for this cycle: OEQA-manual tests for following module: 1.

I think the advantage is not on high end CPUs but more on less powerful ones, so perhaps trying it on something like rpi0 or lower would be good

I went ahead and ran some quick benchmarks myself. Specifically: 1. Running 'free' after things have settled down at boot: a) without prelink core-image-sato-sdk total used

Current Dev Position: YP 3.4 M2 Next Deadline: 12th July 2021 YP 3.4 M2 build Next Team Meetings: Bug Triage meeting Thursday June 17th at 7:30am PDT