prefix test names with libva_

Open
#334 2 comments 0 reactions 0 assignees View on GitHub

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

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from intel/libva-utils

All issues in intel/libva-utils

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.