From: Henning Schild <henning.schild@siemens.com>
To: isar-users <isar-users@googlegroups.com>
Cc: Jan Kiszka <jan.kiszka@siemens.com>
Subject: isar next getting stuck, most likely on ("REPO_ISAR_DIR") + "/isar.lock"
Date: Thu, 9 Sep 2021 10:52:53 +0200 [thread overview]
Message-ID: <20210909105253.71df16d5@md1za8fc.ad001.siemens.net> (raw)
Hi all,
we are seeing isar builds getting stuck when updating from
b78bdb434ef619e13e5c51c74c023fe29c6b3fb6
to
dc36d449dc832db0164f088f3669889557ee015b or beyond.
As of now we did not figure out which patch is causing the issue.
We usually get stuck at some package wanting to do_deploy_deb and then
run into a CI timeout.
2021-09-08 16:56:07 - INFO - NOTE: recipe
linux-perf-5.10-5.10.26-r0: task do_deploy_deb: Started
2021-09-08 17:43:09 - INFO - Bitbake still alive (5000s)
ERROR: Job failed: execution took longer than 3h0m0s seconds
One one occasion we logged into that CI runner and simply deleted
("REPO_ISAR_DIR") + "/isar.lock", which got the build un-stuck.
Investigation is ongoing, just to let people know. Maybe others have
seen that as well.
Henning
next reply other threads:[~2021-09-09 8:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-09 8:52 Henning Schild [this message]
2021-09-14 13:54 ` Anton Mikanovich
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=20210909105253.71df16d5@md1za8fc.ad001.siemens.net \
--to=henning.schild@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.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