From: Uladzimir Bely <ubely@ilbers.de>
To: isar-users@googlegroups.com
Subject: [PATCH 0/3] Detect systemd services ordering cycle
Date: Fri, 16 Aug 2024 17:38:33 +0300 [thread overview]
Message-ID: <20240816144333.27467-1-ubely@ilbers.de> (raw)
Merging v3 of "expand-on-first-boot: Ensure that /tmp is writable"
led to systemd services ordering cycle. Systemd randomly drops one
of sycled services and sometimes it's "expand-on-first-boot" one.
This patchset reverts version 3 of the patch and returns to
previous version.
Additionally, we extend CI so that qemu run tests could always detect
any systemd services ordering cycles.
Clara Kowalsky (1):
expand-on-first-boot: Add /tmp to ConditionPathIsReadWrite
Uladzimir Bely (2):
Revert "expand-on-first-boot: Ensure that /tmp is writable"
testsuite: Detect systemd services ordering cycle
.../expand-on-first-boot/files/expand-on-first-boot.service | 3 +--
testsuite/cibuilder.py | 5 +++++
2 files changed, 6 insertions(+), 2 deletions(-)
--
2.44.2
--
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/isar-users/20240816144333.27467-1-ubely%40ilbers.de.
next reply other threads:[~2024-08-16 14:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-16 14:38 Uladzimir Bely [this message]
2024-08-16 14:38 ` [PATCH 1/3] Revert "expand-on-first-boot: Ensure that /tmp is writable" Uladzimir Bely
2024-08-16 14:38 ` [PATCH 2/3] expand-on-first-boot: Add /tmp to ConditionPathIsReadWrite Uladzimir Bely
2024-08-16 14:38 ` [PATCH 3/3] testsuite: Detect systemd services ordering cycle Uladzimir Bely
2024-08-19 5:17 ` [PATCH 0/3] " Uladzimir Bely
2024-08-21 4:49 ` Uladzimir Bely
2024-08-31 8:45 ` 'Jan Kiszka' via isar-users
2024-09-02 10:02 ` 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=20240816144333.27467-1-ubely@ilbers.de \
--to=ubely@ilbers.de \
--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