From: Romain Naour Date: Mon, 9 Nov 2020 21:25:04 +0100 Subject: [Buildroot] [PATCH] support/testing: TestInitSystemSystemdRwIfupdown test expect a RW rootfs In-Reply-To: <87a6vqs32t.fsf@dell.be.48ers.dk> References: <20201108230009.439548-1-romain.naour@gmail.com> <87a6vqs32t.fsf@dell.be.48ers.dk> Message-ID: <7238eb6c-51b2-cce7-8052-e83fd31a3990@gmail.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net Hello Peter, Le 09/11/2020 ? 21:11, Peter Korsgaard a ?crit?: >>>>>> "Romain" == Romain Naour writes: > > > When running the TestInitSystemSystemdRwIfupdown test, the rootfs must > > be in read-write mode. The commit log [1] introducing systemd tests say > > so: > > > "basic systemd, read-write, network w/ ifupdown" > > > With systemd 246.5, the service systemd-update-done return an error code > > when it can't write on the filesystem (/etc) > > > [1] 117835d5fcd508f301d62dd08ee658c1982c7fa7 > > [2] https://github.com/systemd/systemd/commit/8019995e9af9c6d7b5985198cedccd24eda3e26e > > > Fixes: > > https://gitlab.com/buildroot.org/buildroot/-/jobs/830981813 > > > Signed-off-by: Romain Naour > > Cc: Yann E. MORIN > > --- > > Committed, thanks. > > > Note: systemd-update-done will continue to fail for other systemd tests > > when the rootfs is in read-only mode. > > What is the impact of that? Anything we can do about it? > The systemd-update-done service can't work for read-only filesystem even if previously the service didn't failed in such case. I'll take a look if we can disable it at build time. Best regards, Romain