From: "Hombourger, Cedric" <Cedric_Hombourger@mentor.com>
To: isar-users <isar-users@googlegroups.com>,
Maksim Osipov <mosipov@ilbers.de>,
Jan Kiszka <jan.kiszka@siemens.com>
Subject: Re: Another CI splat: do_cache_base_repo: Failed
Date: Wed, 16 Jan 2019 05:46:21 +0000 [thread overview]
Message-ID: <3893d116-3a06-48e6-b691-f17b7b444daa@Spark> (raw)
In-Reply-To: <4cee612c-4e19-2035-a79b-65aca10f774e@siemens.com>
[-- Attachment #1: Type: text/plain, Size: 2188 bytes --]
Hi Jan,
Sorry - must have missed your earlier e-mail. Let me take a look at the latest code (we anyway need to rebase to the latest now that the feature merge window for our project has been reopened)
Thanks
Cedric
On Jan 16, 2019, 5:29 AM +0100, Jan Kiszka <jan.kiszka@siemens.com>, wrote:
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
[-- Attachment #2: Type: text/html, Size: 3224 bytes --]
next prev parent reply other threads:[~2019-01-16 5:46 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
2019-01-16 5:46 ` Hombourger, Cedric [this message]
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=3893d116-3a06-48e6-b691-f17b7b444daa@Spark \
--to=cedric_hombourger@mentor.com \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.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