According to the schedule [1], Fedora 26 Candidate Beta-1.4 is now available for testing. Please help us complete all the validation testing! For more information on release validation testing, see: https://fedoraproject.org/wiki/QA:Release_validation_test_plan
Test coverage information for the current release can be seen at: https://www.happyassassin.net/testcase_stats/26
You can see all results, find testing instructions and image download locations, and enter results on the Summary page:
https://fedoraproject.org/wiki/Test_Results:Fedora_26_Beta_1.4_Summary
The individual test result pages are:
https://fedoraproject.org/wiki/Test_Results:Fedora_26_Beta_1.4_Installation https://fedoraproject.org/wiki/Test_Results:Fedora_26_Beta_1.4_Base https://fedoraproject.org/wiki/Test_Results:Fedora_26_Beta_1.4_Server https://fedoraproject.org/wiki/Test_Results:Fedora_26_Beta_1.4_Cloud https://fedoraproject.org/wiki/Test_Results:Fedora_26_Beta_1.4_Desktop https://fedoraproject.org/wiki/Test_Results:Fedora_26_Beta_1.4_Security_Lab
All Beta priority test cases for each of these test pages [2] must pass in order to meet the Beta Release Criteria [3].
Help is available on #fedora-qa on irc.freenode.net [4], or on the test list [5].
Current Blocker and Freeze Exception bugs: http://qa.fedoraproject.org/blockerbugs/current
[1] http://fedorapeople.org/groups/schedule/f-26/f-26-quality-tasks.html [2] https://fedoraproject.org/wiki/QA:Release_validation_test_plan [3] https://fedoraproject.org/wiki/Fedora_26_Beta_Release_Criteria [4] irc://irc.freenode.net/fedora-qa [5] https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/ _______________________________________________ test-announce mailing list -- test-announce@lists.fedoraproject.org To unsubscribe send an email to test-announce-leave@lists.fedoraproject.org
On 06/01/2017 06:28 AM, rawhide@fedoraproject.org wrote:
According to the schedule [1], Fedora 26 Candidate Beta-1.4 is now available for testing.
Trying Fedora-Workstation-netinst-i386-26_Beta-1.4.iso on an older i686-netbook fails with this: ... [Failed] Failed to start Switch Root See 'systemctl status initrd-switch-root.service' for details ... Entering emergency mode ...
In "emergency mode": # systemctl status initrd-switch-root.service Failed to map properties: Bad message
Ralf
What is "an older i686-netbook"?
On 06/01/2017 08:21 AM, Ralf Corsepius wrote:
On 06/01/2017 06:28 AM, rawhide@fedoraproject.org wrote:
According to the schedule [1], Fedora 26 Candidate Beta-1.4 is now available for testing.
Trying Fedora-Workstation-netinst-i386-26_Beta-1.4.iso on an older i686-netbook fails with this: ... [Failed] Failed to start Switch Root See 'systemctl status initrd-switch-root.service' for details ... Entering emergency mode ...
In "emergency mode": # systemctl status initrd-switch-root.service Failed to map properties: Bad message
Ralf _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-leave@lists.fedoraproject.org
On 06/01/2017 08:30 AM, Christian Dersch wrote:
What is "an older i686-netbook"?
It's a 2008's Medion Akoya E1210 (To Germans, aka "The Aldi-Netbook"), a rebranded variant of the MSI Wind U100 in a grub/BIOS-multiboot configuration:
With Fedora 25: # cat /proc/cpuinfo model name : Intel(R) Atom(TM) CPU N270 @ 1.60GHz ... flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx constant_tsc arch_perfmon pebs bts aperfmperf pni dtes64 monitor ds_cpl est tm2 ssse3 xtpr pdcm movbe lahf_lm dtherm ...
Fedoras < 26, Ubuntu, Debian all were installable without major probs.
Ralf
On 06/01/2017 08:21 AM, Ralf Corsepius wrote:
On 06/01/2017 06:28 AM, rawhide@fedoraproject.org wrote:
According to the schedule [1], Fedora 26 Candidate Beta-1.4 is now available for testing.
Trying Fedora-Workstation-netinst-i386-26_Beta-1.4.iso on an older i686-netbook fails with this: ... [Failed] Failed to start Switch Root See 'systemctl status initrd-switch-root.service' for details ... Entering emergency mode ...
In "emergency mode": # systemctl status initrd-switch-root.service Failed to map properties: Bad message
Seems to me, as if dracut is segfaulting:
# cat rdsosreport.txt | grep segfault [ 16.346293] localhost kernel: dracut-cmdline[173]: segfault at 805c1000 ip b771c239 sp bfb6a138 error 4 in libc-2.25.so[b75af000+1dd000] [ 20.999957] localhost kernel: dracut-pre-trig[328]: segfault at 81fef000 ip b76d9239 sp bf9cb758 error 4 in libc-2.25.so[b756c000+1dd000]
rpc also seems to be in trouble: # cat rdsosreport.txt | grep rpc ... [ 20.701711] localhost systemd-tmpfiles[300]: Failed to open 'rpcbind.conf': No such file or directory [ 20.703255] localhost dracut-pre-udev[221]: rpcbind: /run/rpcbind/rpcbind.lock: No such file or directory [ 20.731156] localhost rpc.statd[304]: Version 2.1.1 starting [ 20.748734] localhost rpc.statd[304]: Initializing NSM state [ 20.751577] localhost rpc.statd[304]: Running as root. chown /var/lib/nfs/statd to choose different user [ 20.767872] localhost rpc.statd[304]: Failed to register (statd, 1, udp): svc_reg() err: RPC: Remote system error - Connection refused [ 20.784099] localhost rpc.statd[304]: Failed to register (statd, 1, tcp): svc_reg() err: RPC: Remote system error - Connection refused [ 20.800277] localhost rpc.statd[304]: Failed to register (statd, 1, udp6): svc_reg() err: RPC: Remote system error - Connection refused [ 20.816495] localhost rpc.statd[304]: Failed to register (statd, 1, tcp6): svc_reg() err: RPC: Remote system error - Connection refused [ 20.817708] localhost rpc.statd[304]: failed to create RPC listeners, exiting
Ralf
devel@lists.stg.fedoraproject.org
-
Christian Dersch -
Ralf Corsepius -
rawhide＠fedoraproject.org