Between Fedora-Rawhide-20190709.n.1 (when everything was OK) and Fedora-Rawhide-20190711.n.1, i686 images all began failing to boot successfully at all. They all get stuck showing boot messages; live images don't reach a desktop, installer images don't reach the installer.
It seems that multiple bits of systemd (at least systemd-udevd and systemd-journald) all hit the same or similar assertion failure during boot:
Assertion 'clock_gettime(map_clock_id(clock_id), &ts) == 0' failed at ../src/basic/time-util.c:55, function now(). Aborting.
systemd itself did not change between the two composes; my guess at the most likely trigger here is the kernel, which went from kernel-5.2.0-1.fc31 to kernel-5.3.0-0.rc0.git3.1.fc31 . So I'm CC'ing jforbes and labbott.
Note this is not release-blocking as i686 is no longer a release-blocking arch, but as long as we're building the images we should try and make them work...
Let's wait until the merge window closes and we get -rc1 on Sunday/Monday. There's often a lot of churn and I thought there was a regression there although I can't find the thread.
i686 is no longer supported as a bootable image on rawhide/F31 and beyond. Bootable images should no longer be built, and i686 kernels stopped being built on the 13th.
"Bootable images should no longer be built"
Well, they still are being. We got them all in the most recent compose, 20190719.n.1. Clearly someone hasn't shut off a tap somewhere.
Seems lives have been shut off, but installer builds had not. Kevin's going to send a PR for that soon.
OK, that PR is merged, so we should be all good now.