From Fedora Project Wiki

(update the test case urls)
(add webkitgtk test)
Line 42: Line 42:
* [[QA:Testcase_SwapOnZRAM_customconfig]]
* [[QA:Testcase_SwapOnZRAM_customconfig]]
* [[QA:Testcase_SwapOnZRAM_hibernation]]
* [[QA:Testcase_SwapOnZRAM_hibernation]]
* [[QA:Testcase_SwapOnZRAM_buildwkgtk]]


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

Revision as of 00:05, 6 July 2020

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

Date 2020-07-06
Time all week

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?

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

Who's available?

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

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: 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

A list of available test cases:

Reporting bugs

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, probably 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.