From: "MOESSBAUER, Felix" <felix.moessbauer@siemens.com>
To: "isar-users@googlegroups.com" <isar-users@googlegroups.com>,
"Hombourger, Cedric" <cedric.hombourger@siemens.com>
Subject: Re: [PATCH] dpkg: make sbuild timeout configurable
Date: Tue, 14 Nov 2023 19:47:04 +0000 [thread overview]
Message-ID: <1de95bc0ef8a1636c1f5bd8bb684cd4eb4216a54.camel@siemens.com> (raw)
In-Reply-To: <20231114173900.269290-1-cedric.hombourger@siemens.com>
On Tue, 2023-11-14 at 18:39 +0100, 'Cedric Hombourger' via isar-users
wrote:
> Some builds (especially those under qemu) can take a very long time
> and fail only because they did not complete within 2.5 hours. Let
> recipes budget some more time by setting DPKG_BUILD_TIMEOUT to a
> larger value (defaults to 150 minutes like sbuild).
>
> Signed-off-by: Cedric Hombourger <cedric.hombourger@siemens.com>
> ---
> meta/classes/dpkg.bbclass | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/meta/classes/dpkg.bbclass b/meta/classes/dpkg.bbclass
> index d61e9377..4accb076 100644
> --- a/meta/classes/dpkg.bbclass
> +++ b/meta/classes/dpkg.bbclass
> @@ -4,6 +4,11 @@
> inherit dpkg-base
> inherit dpkg-source
>
> +# maximum time (in minutes for the build), override for packages
> requiring
> +# much more time (e.g. when cross-compiling isn't an option /
> supported and
> +# the package large)
> +DPKG_BUILD_TIMEOUT ?= "150"
> +
> DPKG_PREBUILD_ENV_FILE="${WORKDIR}/dpkg_prebuild.env"
>
> # bitbake variables that should be passed into sbuild env
> @@ -94,6 +99,7 @@ dpkg_runbuild() {
> ${@ expand_sbuild_pt_additions(d)}
>
> echo '$apt_keep_downloaded_packages = 1;' >> ${SBUILD_CONFIG}
> + echo '$stalled_pkg_timeout = ${DPKG_BUILD_TIMEOUT};' >>
Hi Cedric,
please add this variable to the dpkg_runbuild[vardepsexclude] as well.
Also I'm wondering if we should document this variable in the docs.
Felix
> ${SBUILD_CONFIG}
>
> DEB_SOURCE_NAME=$(dpkg-parsechangelog --show-field Source --file
> ${WORKDIR}/${PPS}/debian/changelog)
> DSC_FILE=$(find ${WORKDIR} -name "${DEB_SOURCE_NAME}*.dsc" -
> maxdepth 1 -print)
> --
> 2.39.2
>
next prev parent reply other threads:[~2023-11-14 19:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-14 17:39 Cedric Hombourger
2023-11-14 19:47 ` MOESSBAUER, Felix [this message]
2023-11-15 8:41 ` [PATCH v2 0/1] " Cedric Hombourger
2023-11-15 8:41 ` [PATCH v2 1/1] " Cedric Hombourger
2023-11-29 9:22 ` [PATCH v2 0/1] " 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=1de95bc0ef8a1636c1f5bd8bb684cd4eb4216a54.camel@siemens.com \
--to=felix.moessbauer@siemens.com \
--cc=cedric.hombourger@siemens.com \
--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