From Fedora Project Wiki

(update page with better testing instructions, including use of a script i wrote to get system information)
Line 9: Line 9:
}}
}}


{{admon/note | Test Day postponed | Despite the page name, this Test Day will not be happening on 2016-10-26, it is postponed for a few days. We'll decide on a new date and rename the page soon. Stay tuned! We are still working on the test instructions and test cases below, so please wait until they're done before testing!}}
{{admon/note | Test Day postponed from 2016-10-26 | This event was postponed from 2016-10-26. 2016-11-03 is the correct date, so you haven't missed it. Stay tuned! We are still working on the test instructions and test cases below, so please wait until they're done before testing!}}


{{admon/note | 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 [http://bugzilla.redhat.com 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 [[QA/Test_Days|current schedule]] and see if a similar but more recent Test Day is planned or has already happened.}}
{{admon/note | 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 [http://bugzilla.redhat.com 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 [[QA/Test_Days|current schedule]] and see if a similar but more recent Test Day is planned or has already happened.}}
Line 25: Line 25:
== Prerequisite for Test Day ==  
== Prerequisite for Test Day ==  


* An updated [https://getfedora.org/workstation/prerelease Fedora Workstation 25 pre-release], or the Test Day live image.
* An updated installation of a [https://getfedora.org/workstation/prerelease Fedora Workstation 25 pre-release], or a [https://www.happyassassin.net/nightlies.html Fedora 25 nightly image]
* A system with switchable graphics. The [[#switchcheck|{{code|switchcheck}} script]] will error out if you do not have one


== How to test? ==


=== Using an existing Fedora 25 installation ===
=== Using an existing Fedora 25 installation ===


Using an existing Fedora 25 install to test is fine, but please ensure you are using the default GNOME-on-Wayland session (listed as just 'GNOME' in the login screen session chooser). Please also ensure you have at least the following packages updated:
Using an existing Fedora 25 install to test is fine, but please ensure you are using the default GNOME session (listed as just 'GNOME' in the login screen session chooser). Please also ensure you have fully updated the system.
 
It may also be a good idea to create a fresh user account for testing, though issues experienced with your regular user account are also of interest.
 
'''FIXME:''' Should we instruct testers to disable proprietary drivers?


* [http://koji.fedoraproject.org/koji/buildinfo?buildID=808857 gtk3-3.22.1-2.fc25]
=== Live image ===
* [http://koji.fedoraproject.org/koji/buildinfo?buildID=808504 gnome-shell-3.22.1-1.fc25]
* [http://koji.fedoraproject.org/koji/buildinfo?buildID=808842 mutter-3.22.1-2.fc25]


It may also be a good idea to create a fresh user account for testing, though issues experienced with your regular user account are also of interest.
Instead of testing with an installed system, you may download a non-destructive nightly live image for your architecture. Tips on using a live image are available at [[FedoraLiveCD]]. Live image links can be found [https://www.happyassassin.net/nightlies.html here]: please be sure to download one for the correct release. Please boot the live image normally without changing kernel parameters etc.
 
{{anchor|switchcheck}}
=== Download {{code|switchcheck}} and get your system profile ===
 
For this event we have written a script to gather some information on your system. Before running any tests, please download and run the script.
 
{{admon/note|Safety information|The script inspects nothing but your hardware information and whether or not X.org is running, and sends no data out from your system. It is free software and written in Python, so you can easily inspect it before running it if you wish.}}


== How to test? ==
# Install the script by running, at a console: {{command|curl -o /tmp/switchcheck <nowiki>https://pagure.io/fedora-qa/switchcheck/raw/master/f/switchcheck</nowiki> && chmod ugo+x /tmp/switchcheck}}
# Run the script, as a regular user from a terminal in the Workstation desktop: {{command|/tmp/switchcheck}}
#* If it prints an error message with instructions, please follow them.
#* If it prints any other kind of error, please ask for help in IRC.
# If you have switchable graphics and the script works correctly, it should display {{code|Paste the following line as your 'profile' in the results page:}}, and then a line of text. That line of text is your profile.


=== Run the tests ===
=== Run the tests ===


Visit the [http://testdays.fedorainfracloud.org/events/## '''result page is under progress'''] 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. In the ''Profile'' section, please enter your graphics card model number and/or PCI ID. Note the test cases are just starting points: really the goal of this event is for you to exercise the system with your use cases and your hardware, so please do play around beyond what the test cases suggest!
Visit the <!--[http://testdays.fedorainfracloud.org/events/## result page]--> result page '''(currently under construction, link will appear when it's ready)''' 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. In the ''Profile'' section, please enter the profile text produced by [[#switchcheck|the {{code|switchcheck}} script]]. You can add your system's model number before or after the profile text if you like. If you test on multiple systems, please enter a new row of results for each tested system, with the correct profile text for each one.
 


== Reporting bugs ==
== Reporting bugs ==


If you have problems with any of the tests, report a bug to [https://bugzilla.redhat.com Bugzilla]. The component will depend on the bug - it could be the application in which you experienced the problem, or perhaps [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=25&component=gtk3 gtk3], [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=25&component=gnome-shell gnome-shell] or [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=25&component=mutter mutter]. Please ask in IRC if you encountered an issue but are not sure where to report it. Please include your graphics card information in the bug report - you can run {{command|lshw -c display}} or {{command|lspci -nn | grep VGA}}, and paste the output into the bug report.
If you have problems with any of the tests, report a bug to [https://bugzilla.redhat.com Bugzilla]. The component will depend on the bug - '''FIXME: ask Hans for some simple way for people to decide what component to file on'''. Please ask in IRC if you encountered an issue but are not sure where to report it. Please include in the bug report:
# The output of {{command|lshw -c display}} or {{command|lspci -nn | grep VGA}}
# The output of {{command|xrandr --listproviders}}
# The output of {{command|journalctl -b}} (you can run {{command|journalctl -b > /tmp/journal}} and then attach {{filename|/tmp/journal}} to the bug)
# The output of {{command|sudo dmidecode}} (again, you can run {{command|sudo dmidecode > /tmp/dmidecode}} and attach {{filename|/tmp/dmidecode}} to the bug)
'''FIXME: any other stock data, Hans?'''


If you encounter a crash, you should be able to use the [https://github.com/abrt/abrt/wiki/ABRT-Project ABRT] system to file a high-quality bug report. Run {{command|gnome-abrt}} - 'Problem Reporting' in the overview - look for the crash in the list you see, and click the ''Report'' button.
If you encounter a crash, you should be able to use the [https://github.com/abrt/abrt/wiki/ABRT-Project ABRT] system to file a high-quality bug report. Run {{command|gnome-abrt}} - 'Problem Reporting' in the overview - look for the crash in the list you see, and click the ''Report'' button.
Line 53: Line 72:
== Test Results ==
== Test Results ==


[Upcoming Test Day report]
Results will be transferred here from the result page after testing is complete. Please enter results in the <!--[http://testdays.fedorainfracloud.org/events/## result page]--> result page '''(currently under construction, link will appear when it's ready)'''.
 


[[Category:Fedora 25 Test Days]]
[[Category:Fedora 25 Test Days]]

Revision as of 00:49, 1 November 2016

Better Switchable Graphics Support

Date TBA
Time all day

Website QA/Test Days
IRC #fedora-test-day (webirc)
Mailing list test


Test Day postponed from 2016-10-26
This event was postponed from 2016-10-26. 2016-11-03 is the correct date, so you haven't missed it. Stay tuned! We are still working on the test instructions and test cases below, so please wait until they're done before testing!
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.

What to test?

Today's installment of Fedora Test Day will focus on Better Switchable Graphics Support - for Fedora 25, there are some changes to switchable graphics support and today we will be testing that it works well enough, especially for Wayland on Fedora Workstation.

Who's available

The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...

Prerequisite for Test Day

How to test?

Using an existing Fedora 25 installation

Using an existing Fedora 25 install to test is fine, but please ensure you are using the default GNOME session (listed as just 'GNOME' in the login screen session chooser). Please also ensure you have fully updated the system.

It may also be a good idea to create a fresh user account for testing, though issues experienced with your regular user account are also of interest.

FIXME: Should we instruct testers to disable proprietary drivers?

Live image

Instead of testing with an installed system, you may download a non-destructive nightly live image for your architecture. Tips on using a live image are available at FedoraLiveCD. Live image links can be found here: please be sure to download one for the correct release. Please boot the live image normally without changing kernel parameters etc.

Download switchcheck and get your system profile

For this event we have written a script to gather some information on your system. Before running any tests, please download and run the script.

Safety information
The script inspects nothing but your hardware information and whether or not X.org is running, and sends no data out from your system. It is free software and written in Python, so you can easily inspect it before running it if you wish.
  1. Install the script by running, at a console: curl -o /tmp/switchcheck https://pagure.io/fedora-qa/switchcheck/raw/master/f/switchcheck && chmod ugo+x /tmp/switchcheck
  2. Run the script, as a regular user from a terminal in the Workstation desktop: /tmp/switchcheck
    • If it prints an error message with instructions, please follow them.
    • If it prints any other kind of error, please ask for help in IRC.
  3. If you have switchable graphics and the script works correctly, it should display Paste the following line as your 'profile' in the results page:, and then a line of text. That line of text is your profile.

Run the tests

Visit the result page (currently under construction, link will appear when it's ready) 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. In the Profile section, please enter the profile text produced by the switchcheck script. You can add your system's model number before or after the profile text if you like. If you test on multiple systems, please enter a new row of results for each tested system, with the correct profile text for each one.

Reporting bugs

If you have problems with any of the tests, report a bug to Bugzilla. The component will depend on the bug - FIXME: ask Hans for some simple way for people to decide what component to file on. Please ask in IRC if you encountered an issue but are not sure where to report it. Please include in the bug report:

  1. The output of lshw -c display or lspci -nn
  2. The output of xrandr --listproviders
  3. The output of journalctl -b (you can run journalctl -b > /tmp/journal and then attach /tmp/journal to the bug)
  4. The output of sudo dmidecode (again, you can run sudo dmidecode > /tmp/dmidecode and attach /tmp/dmidecode to the bug)

FIXME: any other stock data, Hans?

If you encounter a crash, you should be able to use the ABRT system to file a high-quality bug report. Run gnome-abrt - 'Problem Reporting' in the overview - look for the crash in the list you see, and click the Report button.

Test Results

Results will be transferred here from the result page after testing is complete. Please enter results in the result page (currently under construction, link will appear when it's ready).