Owner: Justin Forbes Time Frame: 5th Jun to 11th Jun Features: Kernel 5.18 rebase
As discussed at Flock, we will start hosting test days for each major kernel rebase (approximately every 8-10 weeks). It was discussed that we should extend this to a test week, to allow time for more participants. They have been incredibly helpful so far. As the 5.18 kernel is now released, I would like to get a test week in before we push the rebase to stable releases. I will have ISOs for USB images so that users can test on bare metal or in VMs, and the kernel will be available in the stabilization repo for users who wish to install it on existing systems.
Metadata Update from @sumantrom: - Issue assigned to sumantrom
Metadata Update from @sumantrom: - Issue set to the milestone: Fedora 37 - Issue tagged with: test days
wiki : https://fedoraproject.org/wiki/Test_Day:2022-06-05_Kernel_5.18_Test_Week
Results : https://testdays.fedoraproject.org/events/136
@jforbes, The test day saw nice traction. However, a complaint about badges has been a thing for some time. Can you please update the ticket with details around participation?
Yes, the badges issue is not so simple. Badges has moved from fedmsg to fedora-messaging, and it requires that the kernel-test site do the same. As the kernel team is just me at this point, I just have not had the cycles to learn the fedora-messaging API and make those changes. It has been raised with CPE, and they are scoping the rewrite/update to make that happen along with a couple of other changes for their hosting of it. When we last met about it, the discussion seemed to indicate the 5.19 kernel test week would be the target. As for this weeks results:
We had 400 total tests run from 124 testers, though there is a lot of overlap in these because I ended up having to build 4 different kernel versions/images over the course of the week. The most a single kernel version got was 148 tests with 39 unique testers. The feedback received was very good quality though, the 5.18.2-201 builds were in direct response to feedback showing a significant performance issue. The largest numbers of tests and testers were with the original and the final images, which works out well.
Thanks again for organizing everything. I will let you know if the badge issue is fixed by the next one so that it can be publicized.
@jforbes, The test day saw nice traction. However, a complaint about badges has been a thing for some time. Can you please update the ticket with details around participation? Yes, the badges issue is not so simple. Badges has moved from fedmsg to fedora-messaging, and it requires that the kernel-test site do the same. As the kernel team is just me at this point, I just have not had the cycles to learn the fedora-messaging API and make those changes. It has been raised with CPE, and they are scoping the rewrite/update to make that happen along with a couple of other changes for their hosting of it. When we last met about it, the discussion seemed to indicate the 5.19 kernel test week would be the target. As for this weeks results: We had 400 total tests run from 124 testers, though there is a lot of overlap in these because I ended up having to build 4 different kernel versions/images over the course of the week. The most a single kernel version got was 148 tests with 39 unique testers. The feedback received was very good quality though, the 5.18.2-201 builds were in direct response to feedback showing a significant performance issue. The largest numbers of tests and testers were with the original and the final images, which works out well. Thanks again for organizing everything. I will let you know if the badge issue is fixed by the next one so that it can be publicized.
Hey Justin,
Thanks for the detailed insight! Love organizing these test weeks and opening up more space for contributors to come and participate! :)
Metadata Update from @sumantrom: - Issue close_status updated to: Worksforme - Issue status updated to: Closed (was: Open)
Metadata Update from @sumantrom: - Issue close_status updated to: Fixed (was: Worksforme)
Login to comment on this ticket.