The kernel team is working on final integration for Linux kernel 5.18. This version was just recently released, and will arrive soon in Fedora. As a result, the Fedora kernel and QA teams have organized a test week now through Sunday, June 12, 2022. Refer to the wiki page for links to the test images you’ll need to participate. Read below for details.
How does a test week work?
A test week is an event where anyone can help make sure changes in Fedora work well in an upcoming release. Fedora community members often participate, and the public is welcome at these events. If you’ve never contributed before, this is a perfect way to get started.
To contribute, you only need to be able to do the following things:
- Download test materials, which include some large files
- Read and follow directions step by step
The wiki page for the kernel test day has a lot of good information on what and how to test. After you’ve done some testing, you can log your results in the test day web application. If you’re available on or around the day of the event, please do some testing and report your results. We have a document which provides all the steps written.
Happy testing, and we hope to see you on test day.
GEPlinux
Hello,
A little fault in the wiki just for fun : F36 instead of f37 🙂
A fully updated F36 test day image or Fedora 35 or 36 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!)
skierpage
The wiki page is quite confusing. “The primary aim is to test on Fedora 35 and 34” but later “Prerequisite for Test Day: A fully updated F36 test day image or Fedora 35 or 36 Workstation/Server installation…” No mention of Fedora 34, or 37. Is the point that this will be the kernel that Fedora 37 uses, even though the kernel team want people running Fedora 35 and 36 to test it?
wayne6001
I think that’s part of what GEPlinux was pointing out. Another one is on the wiki page the link from the first “result page” gets you to the right place to enter results for 5.18, but the second link “results page” gets you to the previous 5.17 results page instead. I think the title of this article was meant to be: “Fedora Linux 36 Test Week for Kernel 5.18” and it is meant to test on F36 or F35.
Leslie Satenstein, Montreal,Que
Had problems to submit my test result. I am using F36KDE spin. Kwin crashed, no dump, nothing to show.
System is an ASUS laptop 8gig ram, nvme drive with lots of space, core I5 10th gen
Kernel 5.18-2-200
skierpage
FWIW I was able to submit test result and the performance test result (which took 2 hours to run). I’m also running Fedora 36 KDE spin.
tcg121268
What hardware did you run the tests on? 2 hours seem a bit long.
travis mechanical man
yepo same here for like a year rando, crashes swaped pc parts out fedora kda 35 and now frezzeing on normal fedora 36 build nothing to show randon bs .This is why i stayed with winder fer so many tyears sadkly but my hatred for it has exceeded just being to lazy to reboot pc every other hour or 15 mins depends what mood the machine is in but the harder its working the faster it crashes sometimes . new to lixus by the way
new old stock build motherboard and high end power supply yep in 2022 LOL CPU :Amd .A8 8650 24 gb ddr3 ram rods ;] 500GB ssd 32 aoc 2k monitor
the stuff does not crash as much or any on ryzen 2700u laptop i barley use
Stephen
Ran the default and performance test on a VM using Gnome Boxes and the provided ISO image. Installation went smooth, testing passed and report submission worked fine. Though my results were uploaded successfully via the test script after completion of both tests, my results do not show up on the results page noted on the test wiki.
Luna bittin Jernberg
Did join in and helped out during the last day today
Tomasz
Guys,
I really lost track.
For now I have on my laptop: Fedora Linux 37 (Workstation Edition Prerelease)
Kernel: vmlinuz-5.19.0-0.rc2.21.fc37.x86_64
I turned on several months ago Rawhide and I use it.
So how can I participate and give you a feedback to the developing release.
But please in points:
1) what to raport?
2) how to raport and to whom?
3) mostly ABRT is not sending errors … because “The backtrace does not contain enough meaningful function frames to be reported. It is annoying but it does not necessarily indicate a problem with your computer. ABRT will not allow you to create a report in a bug tracking system but you can contact kernel maintainers via e-mail.”
Maybe we need some kind of article where it will be pointed out exactly how tests are done, which way and how to contribute.
All the best
T.
Gregory Bartholomew
I’m not a packager, but I think most of the Fedora Workstation development currently happens on mail lists and in IRC chat rooms. However, I think there is a goal of gradually moving from the mail lists to Discourse to make that work a little more visible. My suggestion would be to report any problems that you think might be noteworthy under the workstation tag on Fedora’s Discourse forum: https://discussion.fedoraproject.org/tag/workstation
HTH,
gb
Glenn Johnson
I’m trying to help here but I have no network at all when running Fedora 36 Workstation and the 5.18 kernel.
Rocky
Well done!
Abdul Muqueem
As requested