prefix test names with libva_
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Refactor
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- c
- Domain
- testing-qa
Research direction
Review the listed VA-API test binaries and locate where their names are defined and packaged. Check the upstream status first, then verify that the affected names consistently use the requested libva_ prefix and that package contents reflect the final names.
Written by the indexing model from the issue text.
Description
The binary names could all be prefixed with libva or something like that. Ideally this would be fixed upstream first.
+/usr/bin/av1encode
+/usr/bin/avcenc
+/usr/bin/avcstreamoutdemo
+/usr/bin/h264encode
+/usr/bin/hevcencode
+/usr/bin/jpegenc
+/usr/bin/loadjpeg
+/usr/bin/mpeg2vaenc
+/usr/bin/mpeg2vldemo
+/usr/bin/putsurface
+/usr/bin/putsurface_wayland
+/usr/bin/sfcsample
+/usr/bin/vacopy
+/usr/bin/vavpp
+/usr/bin/vp8enc
+/usr/bin/vp9enc
+/usr/bin/vpp3dlut
+/usr/bin/vppblending
+/usr/bin/vppchromasitting
+/usr/bin/vppdenoise
+/usr/bin/vpphdr_tm
+/usr/bin/vppscaling_csc
+/usr/bin/vppscaling_n_out_usrptr
+/usr/bin/vppsharpness
I was talking about including tests inside the package, but these names are pretty generic, would be ok to prefix them with libva_ ?
- 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