| Line 56: | Line 56: | ||
|- | |- | ||
| [[User:kparal|Kamil Páral]] | | [[User:kparal|Kamil Páral]] | ||
| {{result|warn}} <ref>Asking for runlevel 4 or 2 booted into runlevel 3</ref> <ref>Asking for runlevel 1, single, s, S or -s booted into runlevel "unknown" (as reported by 'runlevel' command)</ref> <ref>ConsoleKit logs doesn't seem to include required information, but testcase documentation is too scarce.</ref> <ref>When booted with console=ttyS0 option, tty1 is not started.</ref> <ref>Error line on poweroff: <code>Stopping rpcbind (via systemctl): /etc/init.d/killall: line 16: 1654 Terminated /etc/init.d/$subsys stop</code></ref> | | {{result|warn}} <ref>Asking for runlevel 4 or 2 booted into runlevel 3</ref> <ref>Asking for runlevel 1, single, s, S or -s booted into runlevel "unknown" (as reported by 'runlevel' command) {{bz|630914}}</ref> <ref>ConsoleKit logs doesn't seem to include required information, but testcase documentation is too scarce.</ref> <ref>When booted with console=ttyS0 option, tty1 is not started.</ref> <ref>Error line on poweroff: <code>Stopping rpcbind (via systemctl): /etc/init.d/killall: line 16: 1654 Terminated /etc/init.d/$subsys stop</code></ref> | ||
| {{result|none}} | | {{result|none}} | ||
| <references/> | | <references/> | ||
Revision as of 10:56, 7 September 2010
| DATE | TIME | WHERE |
| Tue Sept 07, 2010 | All day | #fedora-test-day (webirc) |
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 - which should be linked at QA/Test_Days - and see if a similar but more recent Test Day is planned or has already happened.
What to test?
Today's installment of Fedora Test Day will focus on systemd, the new initialization system being introduced in Fedora 14.
Who's available
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion...
- Development - Lennart Poettering (mezcalero)
- Quality Assurance - Adam Williamson (adamw)
What's needed to test
- An updated Fedora 42 pre-release, or a nightly live image
How to test?
Update your machine
If you're running Fedora 14, make sure you have all the current updates for it installed, using the update manager. If you want to try Rawhide, see the instructions on the Rawhide page on the various ways in which you can install or update to Rawhide. Or:
Live image
Optionally, you may download a non-destructive live image for your architecture. Tips on using a live image are available at FedoraLiveCD. Live images can be found here.
Test
Follow each of these test cases:
Test Results
If you have problems with any of the tests, report a bug to Bugzilla usually for the component systemd. If you are unsure about exactly how to file the report or what other information to include, just ask on IRC and we will help you. Once you have completed the tests, add your results to the Results table below, following the example results from the first line as a template. The first column should be your name with a link to your User page in the Wiki if you have one. For each test case, if your system worked correctly, simply enter the word PASS. If you had trouble, enter the word FAIL, with a footnote indicator, and put a link to the bug report in the References column (as in the example line). For tests you could not perform, enter a dash.
| User | Basic | Tools | References |
|---|---|---|---|
| Sample User |  |
 |
|
| Kamil Páral | |
|