Hi All,
This is the full report for yocto-3.1.16.rc1:
https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults
=== Summary
No high milestone defects.
No new issue found.
Thanks,
Jay
> -Original Message-
> From:
From: Ritesh Harjani
No functionality change as such in this patch. This only refactors the
common piece of code which waits for t_updates to finish into a common
function named as jbd2_journal_wait_updates(journal_t *)
Signed-off-by: Ritesh Harjani
Reviewed-by: Jan Kara
Link:
This is the same as I sent earlier for 5.15.
Two cherry-picks from v5.17-rc3 and v5.18-rc1. The first extracts some
common code into a new function. The second fixes the CVE in this
new function. Merge failure in a comment in jbd2.h had to be fixed.
Code applied cleanly.
Applied to
From: Ritesh Harjani
jbd2_journal_wait_updates() is called with j_state_lock held. But if
there is a commit in progress, then this transaction might get committed
and freed via jbd2_journal_commit_transaction() ->
jbd2_journal_free_transaction(), when we release j_state_lock.
So check for
Greetings,
I tried to add systemd to weston-image-core by adding the following lines in
local.conf:
DISTRO_FEATURES:append = " systemd" VIRTUAL-RUNTIME_init_manager = "systemd"
And indeed, bitbake seems to use them in somve way:
DISTRO_FEATURES="acl alsa argp bluetooth debuginfod ext2 ipv4
*Wiki: *https://wiki.yoctoproject.org/wiki/Bug_Triage
*Attendees: *Akuster, Randy, Richard, Alexandre Belloni, Luca Ceresoli,
Bruce Ashfield, Michael Opdenacker, Ross Burton, Saul Wold, Steve
Sakoman, Valerii, Tim Orling, Joshua Watt
*ARs:*
N/A*
*
*Notes:*
Added AB frequent label,
Add a helper function to check if a given SHA1 hash is an ancestor in
the currently checked out branch, using:
git merge-branch --is-ancestor HEAD
NOTE: This will not match commits which have been cherry-picked.
Signed-off-by: Tim Orling
---
Changes in v2:
* Fix import of
On Thu, 28 Apr 2022 at 15:54, Vasyl Vavrychuk
wrote:
> I did not tried personally but it should work under QEMU too.
>
> > Is it possible to automate with qemu targets?
>
> Depends if QEMU/yocto test automation support screenshots.
> Unfortunately, I don't have expirience with it.
We do need to
Hi, Alex,
Thanks for feedback.
can you explain how this was tested?
In "Implement drm backend" commit I added "--drm" switch to use DRM/KMS
instead of FB in psplash. I use this switch to test by changes, I run
them without this switch to check that FB keeps working too.
Before weston
From: Richard Purdie
This approach didn't work reliably so switch to text based emails
pointing at the website version with graphs and data.
Signed-off-by: Richard Purdie
(cherry picked from commit c0a7cac39acba54e106fa74143c5de7c5eeefab8)
Signed-off-by: Steve Sakoman
---
From: Richard Purdie
Signed-off-by: Richard Purdie
(cherry picked from commit c77f588773924fd724b3c42daace24d6cce50d52)
Signed-off-by: Steve Sakoman
---
scripts/build-perf-test-wrapper | 14 +-
1 file changed, 1 insertion(+), 13 deletions(-)
diff --git
These two patches are required to fix performance builds on the autobuilder.
There will also be a couple of related patches in an upcoming dunfell
oe-core patchset.
The following changes since commit 76cb7aefd0724d59b6c1bbd9fc483e766624cee2:
config.json: Update perf worker target names
On Thursday 28 April 2022 at 09:09:33 +, Martin Weber wrote:
> The software we use (machine/bsp layer level; software level) in
> principal is the same (same upstream, internal or 3rd party), but we need
> to build them in different ways (e.g., one uses system V init, one uses
> systemd init;
Hi Martin,
On 28.04.22 11:09, Martin Weber wrote:
Hi everybody!
We use yocto to build the system for some of our devices. Given we have
multiple use-cases for differing partitions on the device (rescue
system; main system in “release” flavor; main system in “development &
debug” flavor), we
Hi,
On Thu, Apr 28, 2022 at 01:38:35PM +0200, Ayoub Zaki wrote:
> I'm also suing dunfell branch, I did a small modification in
> my_distro_version.bbclass:
>
> def my_distro_version(d):
> > import subprocess
> > project_path = d.getVar('MY_LAYER_BASE', True)
> > cmd = "git describe
On Thu, Apr 28, 2022 at 5:39 AM Jupiter wrote:
>
> Hi Bruce,
>
> Thanks for your response.
>
> > You can't suppress the kernel's config step, it is always going to
> > run. You can't just copy over .config and have the kernel build.
>
> If the OE build kernel config step can be disabled to
I'm also suing dunfell branch, I did a small modification in
my_distro_version.bbclass:
def my_distro_version(d):
> import subprocess
> project_path = d.getVar('MY_LAYER_BASE', True)
> cmd = "git describe --tags"
> proc = subprocess.Popen(cmd, stdout=subprocess.PIPE, shell=True,
>
On Thu, Apr 28, 2022 at 01:25:03PM +0200, Ayoub Zaki wrote:
> Hi,
>
> thanks for the quick reply I tried your suggestion but I get:
>
> ERROR: Unable to parse Var
> Traceback (most recent call last):
> File "Var ", line 1, in
> bb.data_smart.ExpansionError: Failure expanding variable
>
On Thu, 2022-04-28 at 09:09 +, Martin Weber wrote:
> We use yocto to build the system for some of our devices. Given we have
> multiple use-cases for differing partitions on the device (rescue system; main
> system in “release” flavor; main system in “development & debug” flavor), we
> use
Hi,
thanks for the quick reply I tried your suggestion but I get:
ERROR: Unable to parse Var
Traceback (most recent call last):
File "Var ", line 1, in
bb.data_smart.ExpansionError: Failure expanding variable
DISTRO_VERSION[:=], expression was ${@my_distro_version(d)} which triggered
Hi,
On Thu, Apr 28, 2022 at 01:04:22PM +0200, Ayoub Zaki via lists.yoctoproject.org
wrote:
> hello,
>
>
> I would like to have a custom DISTRO_VERSION based on "git describe" of my
> layer:
>
>
> 1) In my layer meta-mylayer/conf/layer.conf, I defined the following:
>
> # Set variable to get
hello,
I would like to have a custom DISTRO_VERSION based on "git describe" of my
layer:
1) In my layer meta-mylayer/conf/layer.conf, I defined the following:
# Set variable to get the location of the layer
> MY_LAYER_BASE := '${LAYERDIR}'
2) I created a my_distro_version.bbclass with
Hi Bruce,
Thanks for your response.
> You can't suppress the kernel's config step, it is always going to
> run. You can't just copy over .config and have the kernel build.
If the OE build kernel config step can be disabled to compile kernel
using customer defconfig, that will make users life
I'm afraid the correct approach to this is indeed several distros.
Yocto, by design, does not support building the same item several
times in a single bitbake invocation.
What you can do, is take a long hard look at the specific differences
between the distros, and see what you can unify. There's
Hi everybody!
We use yocto to build the system for some of our devices. Given we have
multiple use-cases for differing partitions on the device (rescue system; main
system in "release" flavor; main system in "development & debug" flavor), we
use different custom distros for our build.
On Thu, 2022-04-28 at 02:26 +, Anuj Mittal wrote:
> Thanks Chee Yang.
>
> This is the last hardknott release and the branch will no longer be
> actively maintained.
Thanks Anuj for looking after it and everyone else who has contributed.
Cheers,
Richard
-=-=-=-=-=-=-=-=-=-=-=-
Links: You
26 matches
Mail list logo
