From Fedora Project Wiki

(Created page with "{{Infobox_group | name = Fedora Test Day | image = link=QA/Test Days | caption = SwapOnZRAM | date = TBD | time = all week | website = QA/...")
 
m (Adamwill moved page Test Day:F33 SwapOnZRAM to Test Day:2020-07-06 Swap on ZRAM: follow test day page naming convention)
 
(14 intermediate revisions by 4 users not shown)
Line 3: Line 3:
| image = [[File:Echo-testing-48px.png|link=QA/Test Days]]
| image = [[File:Echo-testing-48px.png|link=QA/Test Days]]
| caption = [[SwapOnZRAM]]
| caption = [[SwapOnZRAM]]
| date = TBD
| date = 2020-07-06
| time = all week
| time = all day
| website = [[QA/Test Days]]
| website = [[QA/Test Days]]
| irc = [irc://irc.freenode.net/#fedora-test-day #fedora-test-day] ([http://webchat.freenode.net/?channels=fedora-test-day webirc])
| irc = [irc://irc.freenode.net/#fedora-test-day #fedora-test-day] ([http://webchat.freenode.net/?channels=fedora-test-day webirc])
Line 14: Line 14:
== What to test? ==
== What to test? ==


Today's installment of Fedora Test Day will focus on '''SwapOnZRAM'''.
Today's installment of Fedora Test Day will focus on testing '''[[Changes/SwapOnZRAM]]'''.  


== Who's available? ==
== Who's available? ==


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:chrismurphy|chrismurphy]] (cmurf)
* Development - [[User:chrismurphy|chrismurphy]] (cmurf), [[User:zbyszek|zbyszek]]
* Quality Assurance - [[User:Sumantrom|Sumantro Mukherjee]] (sumantrom), [[User:kparal|Kamil Paral]] (kparal), [[User:coremodule|Geoff]] (coremodule), [[User:adamw|Adam Williamson]] (adamw)
* Quality Assurance - [[User:Sumantrom|Sumantro Mukherjee]] (sumantrom), [[User:kparal|Kamil Paral]] (kparal), [[User:coremodule|Geoff]] (coremodule), [[User:adamw|Adam Williamson]] (adamw)


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


* A virtual machine or a bare metal machine. Using low-memory machines like ARM boards, netbooks or old PCs is very helpful, because it's much easier to run out of available memory on them. But this feature can also be tested on high-performance workstations and servers with lots of RAM.
* Any Fedora Edition or Spin in version 31, 32 or Rawhide.


== How to test? ==
Simple memory hogging test: Open dozens of Firefox tabs, until memory and swap fill up.
Optional: [https://github.com/sergey-senozhatsky/zram-perf-test zram performance testing toolset] This is a bit more complex to get setup and understand the results. But could be useful to confirm/deny the default compression algorithm: lzo-rle is a good default across many architectures and general purpose workloads.


== How to test? ==
=== Run the tests ===
=== Run the tests ===


A list of available test cases:
* [[QA:Testcase_SwapOnZRAM_install]]
* [[QA:Testcase_SwapOnZRAM_install_and_enable]]
* [[QA:Testcase_SwapOnZRAM_stop]]
* [[QA:Testcase_SwapOnZRAM_disable]]
* [[QA:Testcase_SwapOnZRAM_customconfig]]
* [[QA:Testcase_SwapOnZRAM_hibernation]]
* [[QA:Testcase_SwapOnZRAM_buildwkgtk]]


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


If you have problems with any of the tests, have a look in the [http://testdays.fedorainfracloud.org/events/86 results page]. Please include the vulnerability output at the end of the test suite in the comments.  
If you have problems with any of the tests, have a look in the [http://testdays.fedorainfracloud.org/events/86 results page]. Please include the vulnerability output at the end of the test suite in the comments.  
If you don't see it, please file a new bug to [https://bugzilla.redhat.com Bugzilla], probably against <code>ZRAM</code> component.  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 ==
=== Regression Test ===


If you don't see it, please file a new bug to [https://bugzilla.redhat.com Bugzilla], against <code>rust-zram-generator</code> component.  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.


[[Category:Fedora 33 Test Days]]
[[Category:Fedora 33 Test Days]]

Latest revision as of 21:56, 7 July 2020

Fedora Test Day
Echo-testing-48px.png
SwapOnZRAM

Date 2020-07-06
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 testing Changes/SwapOnZRAM.

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 virtual machine or a bare metal machine. Using low-memory machines like ARM boards, netbooks or old PCs is very helpful, because it's much easier to run out of available memory on them. But this feature can also be tested on high-performance workstations and servers with lots of RAM.
  • Any Fedora Edition or Spin in version 31, 32 or Rawhide.

How to test?[edit]

Simple memory hogging test: Open dozens of Firefox tabs, until memory and swap fill up.

Optional: zram performance testing toolset This is a bit more complex to get setup and understand the results. But could be useful to confirm/deny the default compression algorithm: lzo-rle is a good default across many architectures and general purpose workloads.

Run the tests[edit]

A list of available test cases:

Reporting bugs[edit]

If you have problems with any of the tests, have a look in the results page. Please include the vulnerability output at the end of the test suite in the comments.

If you don't see it, please file a new bug to Bugzilla, against rust-zram-generator component. 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.