From Fedora Project Wiki

(Created page with "{{Infobox_group | name = Fedora Test Day | image = link=QA/Test Days | caption = Kernel 4.13 | date = 2017-09-27 | time = all day | website ...")
 
(class the table (sigh))
 
(5 intermediate revisions by 4 users not shown)
Line 20: Line 20:
The following cast of characters will be available for testing, workarounds, bug fixes, and general discussion ...
The following cast of characters will be available for testing, workarounds, bug fixes, and general discussion ...
* Development - [[User:jforbes|jforbes]] (jforbes)
* Development - [[User:jforbes|jforbes]] (jforbes)
* Quality Assurance - [[User:adamw|Adam Williamson]] (admaw), [[User:kparal|Kamil Páral]] (kparal), [[User:Sumantrom|Sumantro Mukherjee]] (sumantrom)
* Quality Assurance - [[User:adamw|Adam Williamson]] (adamw), [[User:kparal|Kamil Páral]] (kparal), [[User:Sumantrom|Sumantro Mukherjee]] (sumantrom), [[User:suprith4989|Suprith Gangawar]] (suprith4989)


== Prerequisites for Test Day ==  
== Prerequisites for Test Day ==  


* A fully updated [test day image] or [https://www.happyassassin.net/nightlies.html Fedora 27 Rawhide image] Workstation/Server installation, either on bare metal or VM (please make sure you have no important data on that installation, things might go wrong -- don't do this on your production machine!)
* A fully updated [https://jforbes.fedorapeople.org/kerneltest.iso test day image] or [https://www.happyassassin.net/nightlies.html Fedora 27 Rawhide image] Workstation/Server installation, either on bare metal or VM (please make sure you have no important data on that installation, things might go wrong -- don't do this on your production machine!)
* Enough free space on HDD
* Enough free space on HDD


Line 30: Line 30:
=== Run the tests ===
=== Run the tests ===


Visit the [http://testdays.fedorainfracloud.org/events/XX 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.
Visit the [http://testdays.fedorainfracloud.org/events/28 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.


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


If you have problems with any of the tests, have a look at the list of reported bugs [https://bugzilla.redhat.com/showdependencytree.cgi?id=1308538&hide_resolved=1 in Bugzilla] and in the [http://testdays.fedorainfracloud.org/events/XX results page]. If you don't see it, please a new bug to [https://bugzilla.redhat.com Bugzilla], probably against <code>kernel</code> component. Add bug [[rhbug:1308538|1308538]] to the ''Blocks:'' field. If you are unsure about exactly how to file the report or what other information to include, just ask on IRC #fedora-test-day or #fedora-qa and we will help you.
If you have problems with any of the tests, have a look at the list of reported bugs [https://bugzilla.redhat.com/showdependencytree.cgi?id=1308538&hide_resolved=1 in Bugzilla] and in the [http://testdays.fedorainfracloud.org/events/28 results page]. If you don't see it, please file a new bug to [https://bugzilla.redhat.com Bugzilla], probably against <code>kernel</code> component. Add bug [[rhbug:1308538|1308538]] to the ''Blocks:'' field. If you are unsure about exactly how to file the report or what other information to include, just ask on IRC #fedora-test-day or #fedora-qa and we will help you.


== Test Results ==
== Test Results ==


Transferred from [http://testdays.fedorainfracloud.org/events/28 results page] 2018-02-01.
=== Regression Test ===
{| class="wikitable"
! User
! Profile
! [http://fedoraproject.org/wiki/QA:Testcase_kernel_regression Regression]
! References
|-
| [[User:Renault|Renault]]
| F27 x86_64 HP Elitebook 8560w
| {{result|pass}}<ref>Default and performance tests passed</ref>
| <references/>
|-
| [[User:alciregi|alciregi]]
| 4.13.3-300.fc27.x86_64 UEFI - default test
| {{result|pass}}
| <references/>
|-
| [[User:alciregi|alciregi]]
| 4.13.3-300.fc27.x86_64 UEFI - performance test
| {{result|pass}}
| <references/>
|-
| [[User:alciregi|alciregi]]
| 4.13.3-301.fc27.armv7hl Raspberry Pi 3
| {{result|pass}}<ref>default, performance and destructive tests passed</ref>
| <references/>
|-
| [[User:alciregi|alciregi]]
| 4.13.3-301.fc27.x86_64 UEFI - default test
| {{result|pass}}
| <references/>
|-
| [[User:baleeiro|baleeiro]]
| 4.13.3-301.fc27.x86_64 stress
| {{result|fail}}<ref>Test suite called with stress
./default/posix_timers                                          PASS   
./default/selinux-dac-controls                                  PASS   
./default/mq-memory-corruption                                  PASS   
./default/cachedrop                                              PASS   
./default/memfd                                                  PASS   
./default/paxtest                                                PASS   
./default/stack-randomness                                      PASS   
./default/sysfs-perms                                            PASS   
./default/timer-overhead                                        PASS   
./default/libhugetlbfs                                          SKIP   
./default/modsign                                                SKIP   
./default/insert_leap_second                                    PASS   
./stress/ltp                                                    FAIL   
./stress/rcutorture                                              PASS   
./thirdparty/nvidia-module                                      PASS   
Test suite complete                                              FAIL
</ref>
| <references/>
|-
| [[User:cialu|cialu]]
| F27 WS x86_64 Box
| {{result|pass}}<ref>Both standard and performance tests passed.</ref>
| <references/>
|-
| [[User:siddharthvipul1|siddharthvipul1]]
| 4.13.3-300.fc27.x86 - F27-20170926
| {{result|pass}}
| <references/>
|-
| [[User:tenk|tenk]]
| KernelTest live image on Asus Laptop
| {{result|pass}}
| <references/>
|-
| [[User:tenk|tenk]]
| KernelTest live image on Virtualbox on Fedora 26 guest
| {{result|pass}}
| <references/>
|-
| [[User:vashirov|vashirov]]
| 4.13.3-300.fc27.x86_64
| {{result|pass}}<ref>default and performance tests passed</ref>
| <references/>
|-
|}


[[Category:Fedora 27 Test Days]]
[[Category:Fedora 27 Test Days]]

Latest revision as of 19:36, 1 February 2018

Fedora Test Day
Echo-testing-48px.png
Kernel 4.13

Date 2017-09-27
Time all day

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


Note.png
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?[edit]

Today's installment of Fedora Test Day will focus on Kernel 4.13

Who's available?[edit]

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

Prerequisites for Test Day[edit]

  • A fully updated test day image or Fedora 27 Rawhide image Workstation/Server installation, either on bare metal or VM (please make sure you have no important data on that installation, things might go wrong -- don't do this on your production machine!)
  • Enough free space on HDD

How to test?[edit]

Run the tests[edit]

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.

Reporting bugs[edit]

If you have problems with any of the tests, have a look at the list of reported bugs in Bugzilla and in the results page. If you don't see it, please file a new bug to Bugzilla, probably against kernel component. Add bug 1308538 to the Blocks: field. If you are unsure about exactly how to file the report or what other information to include, just ask on IRC #fedora-test-day or #fedora-qa and we will help you.

Test Results[edit]

Transferred from results page 2018-02-01.

Regression Test[edit]

User Profile Regression References
Renault F27 x86_64 HP Elitebook 8560w
Pass pass
[1]
  1. Default and performance tests passed
alciregi 4.13.3-300.fc27.x86_64 UEFI - default test
Pass pass
alciregi 4.13.3-300.fc27.x86_64 UEFI - performance test
Pass pass
alciregi 4.13.3-301.fc27.armv7hl Raspberry Pi 3
Pass pass
[1]
  1. default, performance and destructive tests passed
alciregi 4.13.3-301.fc27.x86_64 UEFI - default test
Pass pass
baleeiro 4.13.3-301.fc27.x86_64 stress
Fail fail
[1]
  1. Test suite called with stress ./default/posix_timers PASS ./default/selinux-dac-controls PASS ./default/mq-memory-corruption PASS ./default/cachedrop PASS ./default/memfd PASS ./default/paxtest PASS ./default/stack-randomness PASS ./default/sysfs-perms PASS ./default/timer-overhead PASS ./default/libhugetlbfs SKIP ./default/modsign SKIP ./default/insert_leap_second PASS ./stress/ltp FAIL ./stress/rcutorture PASS ./thirdparty/nvidia-module PASS Test suite complete FAIL
cialu F27 WS x86_64 Box
Pass pass
[1]
  1. Both standard and performance tests passed.
siddharthvipul1 4.13.3-300.fc27.x86 - F27-20170926
Pass pass
tenk KernelTest live image on Asus Laptop
Pass pass
tenk KernelTest live image on Virtualbox on Fedora 26 guest
Pass pass
vashirov 4.13.3-300.fc27.x86_64
Pass pass
[1]
  1. default and performance tests passed