From: Jan Kiszka <jan.kiszka@siemens.com>
To: isar-users <isar-users@googlegroups.com>,
Cedric Hombourger <Cedric_Hombourger@mentor.com>,
Maksim Osipov <mosipov@ilbers.de>
Subject: Re: Another CI splat: do_cache_base_repo: Failed
Date: Wed, 16 Jan 2019 05:29:08 +0100 [thread overview]
Message-ID: <4cee612c-4e19-2035-a79b-65aca10f774e@siemens.com> (raw)
In-Reply-To: <2718374f-01fb-0beb-4b31-08d54d24e19a@siemens.com>
On 07.01.19 16:00, [ext] Jan Kiszka wrote:
> Hi,
>
> Familiar (even if rare)?
>
> NOTE: recipe isar-image-base-1.0-r0: task do_cache_base_repo: Started
> ERROR: mc:qemuarm-stretch:isar-image-base-1.0-r0 do_cache_base_repo: Function
> failed: do_cache_base_repo (log file is located at
> /builds/ebsy/debian/isar/build/tmp/work/debian-stretch-armhf/isar-image-base/temp/log.do_cache_base_repo.55127)
>
> ERROR: Logfile of failure stored in:
> /builds/ebsy/debian/isar/build/tmp/work/debian-stretch-armhf/isar-image-base/temp/log.do_cache_base_repo.55127
>
> Log data follows:
> | DEBUG: Executing shell function do_cache_base_repo
> | The lock file
> '/builds/ebsy/debian/isar/build/downloads/base-apt/db/debian/lockfile' already
> exists. There might be another instance with the
> | same database dir running. To avoid locking overhead, only one process
> | can access the database at the same time. Do not delete the lock file unless
> | you are sure no other version is still running!
> | There have been errors!
> | WARNING: exit code 239 from a shell command.
> | ERROR: Function failed: do_cache_base_repo (log file is located at
> /builds/ebsy/debian/isar/build/tmp/work/debian-stretch-armhf/isar-image-base/temp/log.do_cache_base_repo.55127)
>
> NOTE: recipe isar-image-base-1.0-r0: task do_cache_base_repo: Failed
> ERROR: Task
> (multiconfig:qemuarm-stretch:/builds/ebsy/debian/isar/meta-isar/recipes-core/images/isar-image-base.bb:do_cache_base_repo)
> failed with exit code '1'
>
>
> Cedric, you once sent a related patch ("dpkg: acquire lock when calling
> reprepro") that seems like it was never merged. Was that related to a similar
> error?
Happened again yesterday, and even the retry failed now. Seems we have at least
a better chance to reproduce this... Any comments on this bug?
Jan
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2019-01-16 4:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-07 15:00 Jan Kiszka
2019-01-16 4:29 ` Jan Kiszka [this message]
2019-01-16 5:46 ` Hombourger, Cedric
2019-02-07 12:00 ` Maxim Yu. Osipov
2019-02-07 12:11 ` Hombourger, Cedric
2019-02-07 13:22 ` Hombourger, Cedric
2019-02-07 15:18 ` Maxim Yu. Osipov
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=4cee612c-4e19-2035-a79b-65aca10f774e@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=Cedric_Hombourger@mentor.com \
--cc=isar-users@googlegroups.com \
--cc=mosipov@ilbers.de \
/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