This test never managed to reveal the problem described in [1] because from gnu/system/vm.scm it is seen that our "/tmp" mount is filtered out and replaced with a "/tmp" file-system that is mounted with (needed-for-boot? #t). This last bit is crucial as the problem was caused by the user specified "/tmp" file-system lacking this part which caused "/tmp" being mounted after x11-socket-directory-service has run, effectively shadowing the directory. [1]: <https://issues.guix.gnu.org/57589> * gnu/tests/gdm.scm (%test-gdm-wayland-tmpfs): Delete variable. (make-os): Remove tmpfs? argument. (run-gdm-test): Remove tmpfs? argument. Add a small delay since waiting for gdm.pid is not enough, causing the tests to fail sporadically. Reviewed-by: Josselin Poiret <dev@jpoiret.xyz> Signed-off-by: Maxim Cournoyer <maxim.cournoyer@gmail.com> |
||
|---|---|---|
| .. | ||
| data | ||
| audio.scm | ||
| base.scm | ||
| ci.scm | ||
| cups.scm | ||
| databases.scm | ||
| desktop.scm | ||
| dict.scm | ||
| docker.scm | ||
| file-sharing.scm | ||
| ganeti.scm | ||
| gdm.scm | ||
| guix.scm | ||
| image.scm | ||
| install.scm | ||
| ldap.scm | ||
| lightdm.scm | ||
| linux-modules.scm | ||
| mail.scm | ||
| messaging.scm | ||
| monitoring.scm | ||
| networking.scm | ||
| nfs.scm | ||
| package-management.scm | ||
| reconfigure.scm | ||
| rsync.scm | ||
| samba.scm | ||
| security-token.scm | ||
| security.scm | ||
| singularity.scm | ||
| ssh.scm | ||
| telephony.scm | ||
| version-control.scm | ||
| virtualization.scm | ||
| vnc.scm | ||
| web.scm | ||