On 2/21/24 08:56, Richard Purdie wrote:
> On Wed, 2024-02-21 at 08:53 +0100, Alexis Lothoré wrote:
>> On 2/21/24 08:34, Richard Purdie wrote:
>>> On Tue, 2024-02-20 at 21:01 +0100, Alexis Lothoré via
>>> lists.openembedded.org wrote:
From: Alexis Lothoré
>>
>> [...]
>>
On Wed, 2024-02-21 at 08:53 +0100, Alexis Lothoré wrote:
> On 2/21/24 08:34, Richard Purdie wrote:
> > On Tue, 2024-02-20 at 21:01 +0100, Alexis Lothoré via
> > lists.openembedded.org wrote:
> > > From: Alexis Lothoré
>
> [...]
>
> > >
Hello Richard,
On 2/21/24 08:34, Richard Purdie wrote:
> On Tue, 2024-02-20 at 21:01 +0100, Alexis Lothoré via
> lists.openembedded.org wrote:
>> From: Alexis Lothoré
[...]
>> +##
>> +# General post actions runner
>>
On Tue, 2024-02-20 at 21:01 +0100, Alexis Lothoré via
lists.openembedded.org wrote:
> From: Alexis Lothoré
>
> testimage is able to detect whenever a test run leads to some tests
> failing, and execute some actions in this case. The only action
> currently
> defined in such case is to retrieve
From: Xiangyu Chen
libvirt has added a feature that all sockets for a service being enabled when a
single
one of them is enabled since 9.9.x[1], it likes serviceA enable serviceB,
serviceB enable
serviceA, that cause our systemctl script trap into a dead loop in postinstall
stage,
the error
Hi Michal,
I just noticed the change. I can't find the V2 in my mailbox, so I'm
going to reply here.
I'm a little concerned about forcing such requirement here. It does not
seem *necessary*.
As far as I know, the whole oe-core does not need /tmp to be exec. The
commit message says 'old
Hi,
Le 20/02/2024 à 06:03, Matsunaga-Shinji via lists.openembedded.org a écrit :
> Judgment processing of vulnerable using "=" compares characters as strings
> rather than numbers,
> and misjudges "cases that do not match in strings but do match in numbers" as
> "Patched".
> (e.g. PV = "1.2.0"
From: Bruce Ashfield
Updating linux-yocto/5.4 to the latest korg -stable release that comprises
the following commits:
f0602893f43a Linux 5.4.268
5ff9836ab0f6 arm64: dts: armada-3720-turris-mox: set irq type for RTC
300a55a3a6d4 perf top: Skip side-band event setup if
From: Bruce Ashfield
Updating linux-yocto/5.4 to the latest korg -stable release that comprises
the following commits:
9153fc966495 Linux 5.4.267
69ef165176a3 ASoC: meson: codec-glue: fix pcm format cast warning
584756c3d75a ipv6: remove max_size check inline with ipv4
From: Bruce Ashfield
Updating linux-yocto/5.4 to the latest korg -stable release that comprises
the following commits:
4410df70110f Linux 5.4.266
7d0f1fd80ad6 block: Don't invalidate pagecache for invalid falloc modes
a0678f504758 ring-buffer: Fix wake ups when buffer_percent is set
From: Bruce Ashfield
Updating to the latest korg -stable release that comprises
the following commits:
16e6e107a688 Linux 5.4.264
06bcac5c5151 devcoredump: Send uevent once devcd is ready
c6a1282e530d devcoredump : Serialize devcd_del work
d99376b70247 smb: client: fix
From: Bruce Ashfield
Updating to the latest korg -stable release that comprises
the following commits:
2d21f73b2f16 Linux 5.4.265
5c70542f32af powerpc/ftrace: Fix stack teardown in ftrace_no_trace
0e1867b482b4 powerpc/ftrace: Create a dummy stackframe to fix stack unwind
From: Bruce Ashfield
Updating linux-yocto/5.10 to the latest korg -stable release that comprises
the following commits:
16ad71c250c1 Linux 5.10.209
66e4f4a84791 arm64: dts: armada-3720-turris-mox: set irq type for RTC
2e23761beb90 i2c: s3c24xx: fix transferring more than one message
From: Bruce Ashfield
Updating linux-yocto/5.15 to the latest korg -stable release that comprises
the following commits:
6139f2a02fe0 Linux 5.15.148
84c39986fe6d Revert "Revert "md/raid5: Wait for MD_SB_CHANGE_PENDING in
raid5d""
c8483a4845a0 arm64: dts: armada-3720-turris-mox: set
From: Bruce Ashfield
Data pulled from: https://github.com/nluedtke/linux_kernel_cves
1/1 [
Author: Nicholas Luedtke
Email: nicholas.lued...@uwalumni.com
Subject: Update 3Feb24
Date: Sat, 3 Feb 2024 00:42:14 -0500
]
Signed-off-by: Bruce Ashfield
---
From: Bruce Ashfield
Data pulled from: https://github.com/nluedtke/linux_kernel_cves
1/1 [
Author: Nicholas Luedtke
Email: nicholas.lued...@uwalumni.com
Subject: Update 15Jan24
Date: Mon, 15 Jan 2024 12:48:45 -0500
]
Signed-off-by: Bruce Ashfield
---
From: Bruce Ashfield
Updating linux-yocto/5.15 to the latest korg -stable release that comprises
the following commits:
ddcaf4999061 Linux 5.15.147
231752a0a05d net: usb: ax88179_178a: move priv to driver_priv
d800d18ba132 net: usb: ax88179_178a: remove redundant init code
From: Bruce Ashfield
Updating linux-yocto/5.10 to the latest korg -stable release that comprises
the following commits:
cf13ba74e8eb Linux 5.10.206
2df1e1887c68 spi: atmel: Fix PDC transfer setup bug
2a0a658ed6ef Bluetooth: SMP: Fix crash when receiving new connection when
debug is
From: Bruce Ashfield
Data pulled from: https://github.com/nluedtke/linux_kernel_cves
1/1 [
Author: Nicholas Luedtke
Email: nicholas.lued...@uwalumni.com
Subject: Update 27Dec23
Date: Wed, 27 Dec 2023 19:47:13 -0500
]
Signed-off-by: Bruce Ashfield
---
From: Bruce Ashfield
Updating to the latest korg -stable release that comprises
the following commits:
ca4427ebc626 Linux 5.10.205
05c547e8427a powerpc/ftrace: Fix stack teardown in ftrace_no_trace
e30e62f0e178 powerpc/ftrace: Create a dummy stackframe to fix stack unwind
From: Bruce Ashfield
Updating linux-yocto/5.15 to the latest korg -stable release that comprises
the following commits:
26c690eff0a5 Linux 5.15.146
13578b4ea461 bpf: Fix prog_array_map_poke_run map poke update
339add0430e7 device property: Allow const parameter to dev_fwnode()
From: Bruce Ashfield
Updating to the latest korg -stable release that comprises
the following commits:
d93fa2c78854 Linux 5.15.145
ee41f667aa64 kasan: disable kasan_non_canonical_hook() for HW tags
f30f893143b9 tracing/kprobes: Return EADDRNOTAVAIL when func matches
several
From: Bruce Ashfield
Updating to the latest korg -stable release that comprises
the following commits:
d330ef1d295d Linux 5.10.203
9c957e2b5254 driver core: Release all resources during unbind before
updating device links
2325d3b6b10f r8169: fix deadlock on RTL8125 in jumbo mtu
From: Bruce Ashfield
Updating to the latest korg -stable release that comprises
the following commits:
8a1d809b0545 Linux 5.15.142
4d9bd1b108d7 iomap: update ki_pos a little later in iomap_dio_complete
6ed02493ef14 r8169: fix deadlock on RTL8125 in jumbo mtu mode
0249024aa48e
From: Bruce Ashfield
Updating linux-yocto/6.1 to the latest korg -stable release that comprises
the following commits:
8b4118fabd6e Linux 6.1.78
1296c110c5a0 netfilter: nft_set_rbtree: skip end interval element from gc
d89a80e4827d net: stmmac: xgmac: fix a typo of register name in
From: Bruce Ashfield
Data pulled from: https://github.com/nluedtke/linux_kernel_cves
1/1 [
Author: Nicholas Luedtke
Email: nicholas.lued...@uwalumni.com
Subject: Update 9Feb24
Date: Fri, 9 Feb 2024 18:02:45 -0500
]
Signed-off-by: Bruce Ashfield
---
From: Bruce Ashfield
Updating linux-yocto/6.6 to the latest korg -stable release that comprises
the following commits:
b2c9bf06474e Linux 6.6.17
b734f7a47aeb netfilter: nft_set_rbtree: skip end interval element from gc
d850a1f8dbbe net: stmmac: xgmac: fix a typo of register name in
From: Bruce Ashfield
Data pulled from: https://github.com/nluedtke/linux_kernel_cves
1/1 [
Author: Nicholas Luedtke
Email: nicholas.lued...@uwalumni.com
Subject: Update 9Feb24
Date: Fri, 9 Feb 2024 18:02:45 -0500
]
Signed-off-by: Bruce Ashfield
---
Hi All,
QA for yocto-4.3.3.rc1 is completed. This is the full report for this release:
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,
Jing Hui
>
So far it was assumed that it was detected ok for target recipe but
actually it ends up with warnings and build moves on, however with
gcc-14 these warnings are treated as errors and we see the problem even
with target recipes.
Signed-off-by: Khem Raj
---
meta/recipes-core/ncurses/ncurses.inc |
From: Joe Slater
Allow interface renaming if 'pni-names' is a distro
feature.
We do not add QB_NO_PNI to QB_CMDLINE_IP_SLIRP because
renaming was never suppressed for slirp.
Signed-off-by: Joe Slater
---
meta/classes-recipe/qemuboot.bbclass | 7 ++-
1 file changed, 6 insertions(+), 1
Looking at qemurunner.py, it seems it will not find the ip info if net.ifnames
precedes it. I will submit a V2 of the patch.
Joe
> -Original Message-
> From: Alexandre Belloni
> Sent: Tuesday, February 6, 2024 11:12 AM
> To: Slater, Joseph
> Cc:
From: Alexis Lothoré
In order to debug issues related to disk space (see [1]), add a failed
tests post action to retrieve disk usage on the target. Rely on the test
context object to run the corresponding command onto the target
[1] https://bugzilla.yoctoproject.org/show_bug.cgi?id=15220
From: Alexis Lothoré
Since the target under test can be a virtualized guest, when some tests
fail because of disk usage (see [1]), also fetch disk usage statistics from
host to allow checking whether a host disk space saturation could affect
running tests.
[1]
Hello,
this small series is related to some disk space issue observed by the SWAT
team (see [1]) which eventually leads to tests failure. In order to help
diagnose those issues, I propose to enrich the retrieved artifacts with
some additional data, like disk usage on target and on host (in case
From: Alexis Lothoré
In order to be able to create actions that could store new files during
failed test post actions, we need to split artifacts directory creation
from artifacts retrieval.
Create a new dedicated action to create artifacts main directory so we can
add actions creating files in
From: Alexis Lothoré
testimage is able to detect whenever a test run leads to some tests
failing, and execute some actions in this case. The only action currently
defined in such case is to retrieve artifacts from the target under test,
as listed in TESTIMAGE_FAILED_QA_ARTIFACTS
In order to be
On Tue, 20 Feb 2024 at 14:14, Alexander Kanavin via
lists.openembedded.org
wrote:
> As far as I understand it's only those embedded tests that are
> problematic, and other kinds of tests (e.g. modular tests) don't
> affect how the library is built. So perhaps you can make a patch that
> passes
There was a report that enabling assertions and all tests results in
notices in log.do_configure:
NOTE: building with unit tests increases the size of the installed library and
renders it insecure.
NOTE: building with assertions increases library size and decreases performance.
This was
On 2024-02-20 06:33, Richard Purdie wrote:
On Mon, 2024-02-19 at 09:30 -0800, Tim Orling wrote:
Replace the deprecated setuptools3 bbclass with python_mesonpy.
The build-backend has been defined as "mesonpy" since:
https://github.com/numpy/numpy/commit/942fb8caf33a65e449fbf198ecf1cd39be953248
Current Dev Position: YP 5.0 M3 - Feature Freeze
Next Deadline: 19th February 2024 YP 5.0 M3 build
Next Team Meetings:
-
Bug Triage meeting Thursday February 22nd at 7:30 am PST (
https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
-
Weekly Project Engineering
Thank you for your submission. Patchtest identified one
or more issues with the patch. Please see the log below for
more information:
---
Testing patch
/home/patchtest/share/mboxes/1-2-numactl-Upgrade-2.0.17---2.0.18.patch
FAIL: test commit message presence: Please include a commit message on
Update one of the patches to account for upstream changes.
Signed-off-by: Richard Purdie
---
.../0001-Makefile.am-update-rpath-link.patch | 12 +---
...g-ust-common-link-with-liburcu-explicitly.patch | 7 ---
...gust-Makefile.am-Add-install-lib-to-setup.patch | 14
Signed-off-by: Richard Purdie
---
.../numactl/numactl/0001-define-run-test-target.patch | 8 ++--
.../numactl/numactl/Fix-the-test-output-format.patch | 3 ++-
meta/recipes-support/numactl/numactl_git.bb | 4 ++--
3 files changed, 10 insertions(+), 5 deletions(-)
diff
From: Alexis Lothoré
Despite managing to retrieve the failed ptests artifacts, testimage seems
to dump some retrieval errors like the following one:
WARNING: core-image-ptest-valgrind-1.0-r0 do_testimage: Can not retrieve
/usr/lib/valgrind/ptest from test target
Log the corresponding exception
On Tue, 20 Feb 2024 at 13:35, Steffen Olsen wrote:
> We are currently in the process of examining a memory leak in systemd, which
> has led us to investigate how dbus is built for our targets (we are currently
> using Kirkstone).
>
> When kirkstone was introduced, there was made a couple of
On Mon, 2024-02-19 at 17:55 +0100, Enguerrand de Ribaucourt wrote:
> Among the files generated by meson is compile_commands.json. It is not
> used by bitbake during the build. However, if the devtool workspace is
> opened inside an IDE, that IDE can use compile_commands.json to
> configure linting
Hi,
We are currently in the process of examining a memory leak in systemd, which
has led us to investigate how dbus is built for our targets (we are currently
using Kirkstone).
When kirkstone was introduced, there was made a couple of changes in how dbus
is built (oe-core cfecef (
On Mon, 2024-02-19 at 09:30 -0800, Tim Orling wrote:
> Replace the deprecated setuptools3 bbclass with python_mesonpy.
>
> The build-backend has been defined as "mesonpy" since:
> https://github.com/numpy/numpy/commit/942fb8caf33a65e449fbf198ecf1cd39be953248
>
> The vendored meson-python was
Fixes [YOCTO #15120]
Consider OVERLAYFS_WRITABLE_PATHS as dependecy of do_create_overlayfs_units() in
order to rebuild the recipe when changing the used mount point.
Tested in a local recipe by changing the used mount point and verified that the
recipe was re-build: passed
Signed-off-by:
Without any of my modifications, it seems that glibc-locale recipe creates
a glibc-locale-locale.alias package containing only the file
/usr/share/locale/locale.alias. It looks like the same issue revealed with
the CUPS recipe. Do you know in which package locale.alias file is expected
to be
Hi Adrian,
Thanks for your review.
Yes it doesn't makes a lot of sense to keep this patch compared to the
specific support you are working on. It was especially useful for
recipes using plain oe_runmake or CC/CXX outside of a class. But we
can't distinguish these recipes from others classes
Hi Enguerrand
I would really like to stay on the path with tests. This patch changes
code which is covered by tests without tests. Lets develop the
autotools support as a separate patch series.
There are three parts needed:
- Extend the cpp-example with autotools support (already on my branch)
On Mon, 2024-02-19 at 17:55 +0100, Enguerrand de Ribaucourt wrote:
> When debugging or browsing files, the user may fall into external
> sources from other packages in the sysroot or dbg-rootfs. Modifying
> them
> will only lead to confusion since they will be overwritten by Yocto.
> The
> user
On Mon, 2024-02-19 at 17:55 +0100, Enguerrand de Ribaucourt wrote:
> The generated scripts use the sys.path configuration found inside
> bitbake. It can be a different python version than the one used on
> the
> host through the IDE.
>
> For instance, when running the generated script
>
On Mon, 2024-02-19 at 17:55 +0100, Enguerrand de Ribaucourt wrote:
> When launching the debug configuration, the source files from the
> debug
> rootfs were openened in the editor instead of the local workspace
> files.
> We add an exception to properly map them to the file being developed
> and
>
56 matches
Mail list logo
