From: Baurzhan Ismagulov <ibr@radix50.net>
To: isar-users <isar-users@googlegroups.com>
Subject: Re: Sporadic build failure of next
Date: Tue, 20 Aug 2019 12:31:40 +0200 [thread overview]
Message-ID: <20190820103140.GI3412@yssyq.m.ilbers.de> (raw)
In-Reply-To: <1caa3be8-d9c7-0f31-7cb7-4ee3ad43af27@siemens.com>
Hello Jan,
On Tue, Aug 20, 2019 at 07:37:04AM +0200, Jan Kiszka wrote:
> attached a build failure of 49895c62cdca. I ran that build 3 more times, but
> it didn't trigger an issue again. Looks like some false sharing, but I do
> not have an idea yet of what exactly.
Thanks for heads-up.
ERROR: mc:de0-nano-soc-stretch:libhello-0.1-98f2e41-r0 do_build: Function failed: do_build (log file is located at /builds/ebsy/debian/isar/build/tmp/work/debian-stretch-armhf/libhello-0.1-98f2e41-r0/temp/log.do_build.56623)
...
ERROR: mc:qemuarm-stretch:libhello-0.1-98f2e41-r0 do_build: Function failed: do_build (log file is located at /builds/ebsy/debian/isar/build/tmp/work/debian-stretch-armhf/libhello-0.1-98f2e41-r0/temp/log.do_build.69020)
Apparently, we instruct multiconfig to run the same task twice for the same
DISTRO and DISTRO_ARCH in the same directory, and they happen to run in
parallel. If this is the case, we should ideally build once; not sure whether
this is desirable for all packages, though (e.g., two boards building the
kernel from the same source and revision, but with different configs, etc.).
I couldn't find the same failure on ci.i-b.o, but I remember some issues around
this (related or not).
Could we force building of the packages at the same time in CI? Ideas welcome.
In this way, we could perform regression testing for concurrency.
IIRC, the kernel or PREEMPT_RT has a static checker that can detect potential
deadlocks. That would be a nice addition to bitbake (although I doubt it is
implementable today, since it would require recipe introspection w.r.t. e.g.
build directory, etc.).
With kind regards,
Baurzhan.
next prev parent reply other threads:[~2019-08-20 10:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-20 5:37 Jan Kiszka
2019-08-20 6:54 ` Claudius Heine
2019-08-20 7:09 ` Jan Kiszka
2019-08-20 7:37 ` Claudius Heine
2019-08-20 10:31 ` Baurzhan Ismagulov [this message]
2019-08-20 10:40 ` Jan Kiszka
2019-08-20 11:05 ` Baurzhan Ismagulov
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=20190820103140.GI3412@yssyq.m.ilbers.de \
--to=ibr@radix50.net \
--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