gronod/lfs
1
0
Fork 0
mirror of https://git.linuxfromscratch.org/lfs.git synced 2025-01-18 04:57:38 +00:00
Code Issues Packages Projects Releases Wiki Activity

Revert "systemd: Update the test suite failures list for 257."

Browse Source 
This reverts commit 8f493a6377.

When I was building LFS, I somehow forgot to mount /dev/sdb7 to
/mnt/lfs on my system. I ended up chrooting into /mnt/lfs, and it was a
directory, not a filesystem.

This happens from time to time, not sure why I did it this time!

The tests that I had marked as failed no longer fail, but at the same
time, now test-namespace does. Let's undo this commit...
This commit is contained in:
Douglas R. Reno 2024-12-19 15:05:20 -06:00
parent 8f493a6377
commit 33b3a04e4e
1 changed files with 3 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
chapter08/systemd.xml
View File

@ -225,14 +225,9 @@ meson setup .. \
ninja test</userinput></screen>
<!-- test-namespace needs /run/systemd/inaccessible/sock, which only exists
after initializing the system with systemd.
This seems to pass now in chroot -->
<!-- test-fd-util, test-mount-util, and test-mountpoint-util seem to fail
due to being unable to remount the root directory as MS_SLAVE. -->
<para>Three tests named <literal>systemd:test / test-fd-util</literal>,
<literal>systemd:test / test-mount-util</literal>, and
<literal>systemd:test / test-mountpoint-util</literal>,
are known to fail in the LFS chroot environment. Some other tests may
after initializing the system with systemd. -->
<para>One test named <literal>systemd:core / test-namespace</literal>
is known to fail in the LFS chroot environment. Some other tests may
fail because they depend on various kernel configuration options.</para>
<para>Install the package:</para>