m (→How to test?) |
mNo edit summary |
||
| Line 29: | Line 29: | ||
* A virtual machine or a bare metal machine | * A virtual machine or a bare metal machine | ||
* An installation of Fedora 34 (any Edition or Spin). Make sure to fully update your system. If installing a fresh system, it's recommended to use the latest [https://www.happyassassin.net/nightlies.html nightly image]. | * An installation of Fedora 34 (any Edition or Spin). Make sure to fully update your system. If installing a fresh system, it's recommended to use the latest [https://www.happyassassin.net/nightlies.html nightly image]. | ||
** Ensure your installation is running systemd 248~ | ** Ensure your installation is running systemd 248~rc4 or higher (by running `systemctl --version`). | ||
== How to test? == | == How to test? == | ||
Revision as of 01:27, 19 March 2021
| Systemd-oomd Test Week | |
|---|---|
| |
| Date | 2021-03-18 to 2021-03-25 |
| Time | all day |
| Website | QA/Test Days |
| IRC | #fedora-test-day (webirc) |
| Mailing list | test |
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?
This Test Day will focus on Enabling systemd-oomd by default for all variants - a Change for Fedora 34 that replaces EarlyOOM, a process based user space out of memory (OOM) killer with systemd-oomd, a cgroups v2 based user OOM killer.
Who's available
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion:
- Development - Anita Zhang, Davide Cavalca, Michel Salim, Tejun Heo, Rik van Riel
- Quality Assurance - Sumantro Mukherjee (sumantrom), Geoffrey Marr (coremodule), Kamil Paral (kparal), Adam Williamson (adamw)
You can chat with us on IRC. See the infobox on top of the page to learn the right IRC channel.
Prerequisite for Test Day
- A virtual machine or a bare metal machine
- An installation of Fedora 34 (any Edition or Spin). Make sure to fully update your system. If installing a fresh system, it's recommended to use the latest nightly image.
- Ensure your installation is running systemd 248~rc4 or higher (by running
systemctl --version).
- Ensure your installation is running systemd 248~rc4 or higher (by running
How to test?
Visit the results 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.
Please also try to experiment and explore and perform tasks not mentioned in any of the pre-defined test cases. We would love to get more data on how to tweak systemd-oomd for your workloads. Please comment on any unexpected kills from systemd-oomd as well.
Reporting bugs
All bugs should be reported into Bugzilla, in most cases against the oomd component. Please include the output of oomctl, uname -a, systemctl --version, and relevant log lines from sudo journalctl -r to aid in debugging. Additional information about your system such as your swap configuration, and available memory would also be helpful.
If you are unsure about exactly how to file the report or what other information to include, just ask us on IRC (see instructions above).
Test Results
Test results will be exported here once the test day is over. See How to test? section for information how to submit results and see the live results.