From: Uladzimir Bely <ubely@ilbers.de>
To: isar-users@googlegroups.com
Subject: [PATCH 4/5] meta/bitbake.conf: Use custom disk usage command for buildstats
Date: Fri, 12 Jan 2024 07:12:56 +0100 [thread overview]
Message-ID: <20240112061257.22241-5-ubely@ilbers.de> (raw)
In-Reply-To: <20240112061257.22241-1-ubely@ilbers.de>
In Isar, default "du -sh" disk usage command produces multiple
"Permission denied" warnings. Contrary to OE, Isar uses "sudo"
for rootfs creation and some path may be not available.
Also, some subpaths of rootfs may be mounted during statistics
collecting, so we have to limit "du" by one filesystem.
Signed-off-by: Uladzimir Bely <ubely@ilbers.de>
---
meta/conf/bitbake.conf | 2 ++
1 file changed, 2 insertions(+)
diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
index 80dc01c7..a90edc4b 100644
--- a/meta/conf/bitbake.conf
+++ b/meta/conf/bitbake.conf
@@ -159,6 +159,8 @@ INHERIT += "isar-events sstate"
# Buildstats requires IMAGE_ROOTFS to be always defined
IMAGE_ROOTFS ??= "${WORKDIR}/rootfs"
INHERIT += "${@'buildstats' if d.getVar('USE_BUILDSTATS') == '1' else ''}"
+# Use custom disk usage command to avoid "Permission denied" warnings
+BUILDSTATS_DISK_USAGE_CMD = "sudo du -shx"
# Default values for ccache
USE_CCACHE ??= "0"
--
2.20.1
next prev parent reply other threads:[~2024-01-12 6:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-12 6:12 [PATCH 0/5] Improve buildstats functionality Uladzimir Bely
2024-01-12 6:12 ` [PATCH 1/5] buildstats: Sync code base with openembedded-core 2022-04.15 Uladzimir Bely
2024-01-12 6:12 ` [PATCH 2/5] buildstats: consider multiconfigs when collecting statistics Uladzimir Bely
2024-01-12 6:12 ` [PATCH 3/5] buildstats: support of custom disk usage command Uladzimir Bely
2024-01-12 6:12 ` Uladzimir Bely [this message]
2024-01-12 6:12 ` [PATCH 5/5] buildstats: Collect build statictics by default Uladzimir Bely
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240112061257.22241-5-ubely@ilbers.de \
--to=ubely@ilbers.de \
--cc=isar-users@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox