Hi! Mathieu Othacehe skribis: >> + `((swap-devices (list ,@(map (lambda (uuid) >> + `(uuid ,uuid)) >> + uuids)))))) > > I fear that this will break the "gui-installed-os" test. The > "installation-target-os-for-gui-tests" procedure declares "/dev/vda2" as > swap-device, while the installer will declare it using an UUID. > > This mismatch will probably make "shepherd services" test unhappy. We > could maybe set a swap label during installation and use it in the > installer tests? Good point, I had overlooked that. I came up with the following trick: during installation, once user partitions are formatted, we set a pre-defined UUID on /dev/vda2, and we use that label in ‘installation-target-os-for-gui-tests’. It works, but I think it’s racy: the config file could be generated before we’ve changed the UUID. Problem is that since formatting is the last step that occurs before config file generation, there’s no synchronization point where the installer could wait for the client (i.e., wait until the client has run ‘swaplabel’.) Ideas? Thanks, Ludo’.