extend testing with real Intel GPUs as part of the CI process
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
Start by reviewing the libva tests and the existing Mesa3D CI setup. Determine how real Intel GPU testing could connect to the current GitHub workflow, including whether mirroring libva-utils on Freedesktop GitLab is needed. Done means the integration approach is defined and the tests run on real Intel GPUs as part of CI.
Written by the indexing model from the issue text.
Description
Would you be interested to extend testing on hardware e.g. Intel GPUs?
If yes, we would accept connecting the libva tests to the existing Mesa3D CI. What I see as a challenge, is the GitHub x GitLab. Anyway this part could be handled by mirroring libva-utils on Freedesktop Gitlab.
I would love to hear what you think about it.
- Dominant language
- C
- Stars
- 244
- Forks
- 175
- Avg merge
- 9d 7h
- Merged PRs (30d)
- 1
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from intel/libva-utils
-
av1encode: reference_frames[2..7] left as surface 0 (memset only covers 8 bytes)Possibly taken @0z5a claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
intel/libva-utils#390 ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
intel/libva-utils#387 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
intel/libva-utils#378 · 6 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
intel/libva-utils#376 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
intel/libva-utils#374 ·
All issues in intel/libva-utils
Similar issues
-
ecs_ptr_from_json does not free the buffer of a string longer than 256 bytes on two error pathsOpen
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
SanderMertens/flecs#2444 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Cisco-Talos/clamav#1941 ·
Maintainers usually reply within 2 days
-
Status: Opened
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
espressif/esp-eth-drivers#201 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 74/100
libsdl-org/SDL#16788 ·
Maintainers usually reply within 1 day