Test Day:2024-04-09 Intel Open CL

Intel OpenCL
Date	2024-04-09
Time	all day
Website	QA/Test Days
Matrix	#test-day:fedoraproject.org(other clients|?)
Mailing list	test

Can't make the date?
If you come to this page 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, 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 OpenCL

Who's available

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

• Development - Frantisez (Frantisez)
• Quality Assurance - Sumantro Mukherjee (sumantrom), Geoffrey Marr (coremodule), Kamil Paral (kparal), Adam Williamson (adamw)

You can chat with us on Matrix. See the infobox on top of the page to learn where to join.

Prerequisite for Test Day

• A virtual machine or a bare metal machine
• An installation of Fedora 40 (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.

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.

Reporting bugs

Perhaps you've found an already-reported bug. Please look at:

• Fedora 40 Beta blocker bugs
• Fedora 40 Final blocker bugs

All new bugs should be reported into the FIXME upstream bug tracker. A less-preferred alternative is to file them into Red Hat Bugzilla, in most cases against the FIXME component.

We really need bug reports!
Please note that just mentioning your problem into the comments section on the results page is not very helpful. Very often those problems only happen in specific circumstances, or with specific steps taken. We need the logs and screenshots, and we need to be able to ask you followup questions. Please file bug reports, it's much more useful than a short comment. Thank you!

When filing the bug, it's very helpful to include:

• exact steps you've performed (and whether you can reproduce it again)
• screenshots or videos, if applicable
• system journal (log), which you can retrieve by journalctl -b > journal.txt
• all output in a terminal, if started from a terminal
• your system description

If you are unsure about exactly how to file the report or what other information to include, just ask us.

Please make sure to link to the bug when submitting your test result, thanks!

Test Results

Basic

User	Profile	OpenCL basic	OpenCL apps	References
frantisekz	Intel UHD Graphics 630	pass
lbrabec	Intel UHD Graphics 620	pass
webfiction	Intel Iris Xe Graphics	pass