Can't make the date? If you come to this page before or after the test day is completed, your testing is still valuable, and you can use the information on this page to test, file any bugs you find at Bugzilla, and add your results to the results section. If this page is more than a month old when you arrive here, please check the current schedule and see if a similar but more recent Test Day is planned or has already happened.

Documentation is also available here. Documentation feedback is welcome through chat, mailing list, or as an issue. NOTE: there is a known issue about the links on the obtaining images page. For the test day, please use the images specified below!

Visit the result page and click on the column title links to see the tests that need to be run: most column titles are links to a specific test case. Follow the instructions there, then enter your results by clicking the Enter result button for the test.

↑1. Installed with default settings, including the default disk layout. Only set the root password during the install phase, did not create a standard user account. After reboot, the initial setup utility runs automatically, as it should, user creation was successful. Also, login with the newly created account works as expected.

↑during install, changed timezone (defaulted to Central?), auto partition. Set root password but did not create a user.
Created user with password and as admin during inital setup dialog. All worked as expected.

↑I reset SD card with more options: --image=Fedora-IoT-30-20190312.1.aarch64.raw.xz --target=rpi3 --media=/dev/mmcblk0 --resizefs --addconsole --addkey=/home/susan/.ssh/id_rsa.pub --args "console=tty0"
The resizefs worked as did the addkey. addconsole does make sure that the config.txt has enable_uart=1 but nothing gets added to the grub console line for the console. There is a "sed: can't read /tmp/boot/extlinux/extlinux.conf: No such file or directory" message which is expected since this file does not exist. no console=tty0 in any of the /boot config files or after booting in cat /proc/cmdline.

↑Used HDMI for display. No serial console configured.
initial boot with wired lan but wifi tests work great!
bluetooth service "inactive (dead)" I was able to systemctl start bluetooth but bluetoothctl still shows "No default controller available".

↑To use the serial console I added 'console=ttyS1,115200 console=tty0' to the bls snippet (/boot/loader/entries/ostree-1-fedora-iot.conf) . This gave working output on display and serial console. Wifi working. Bluetooth failed to start at boot.