Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

~2000 test failures in test_va_api #16

Closed
uartie opened this issue Dec 7, 2017 · 9 comments
Closed

~2000 test failures in test_va_api #16

uartie opened this issue Dec 7, 2017 · 9 comments

Comments

@uartie
Copy link
Contributor

uartie commented Dec 7, 2017

test_va_api is part of https://github.com/01org/libva-utils and is used for simple VA API conformance validation. Currently, when executed with LIBVA_DRIVER_NAME=iHD there are ~2000 test failures. Some test failures are inevitable (since they may be specific to i965 driver), but many others are real failures.

FYI... i965 driver has 0 failures in test_va_api as of writing.

@uartie
Copy link
Contributor Author

uartie commented Dec 7, 2017

#12 and #15 are related to some of these failures

@XinfengZhang
Copy link
Contributor

some test in libva-utils is not correct. such as test_va_api_fixture.cpp:117, why the value must is 32, it should be 38 with current libva master

@uartie
Copy link
Contributor Author

uartie commented Dec 7, 2017

some test in libva-utils is not correct. such as test_va_api_fixture.cpp:117, why the value must is 32, it should be 38 with current libva master

Please test with latest libva-utils master... this was fixed for about a week now (intel/libva-utils@5975415). There are also various other fixes to libva-utils to make it more driver agnostic.

If you discover other issues with the tests themselves... can you kindly file a new issue in the libva-utils project? I am also attempting to identify/fix some of the failures as time permits.

@XinfengZhang
Copy link
Contributor

now, still 1689 failed cases. will continue, it should be a long term task.

@XinfengZhang
Copy link
Contributor

after merging PR 56 , still 1450 failure exist.

@XinfengZhang
Copy link
Contributor

when call vaCreateConfig for encode. if VAConfigAttribRateControl is not set, is "not supported" expected.

@XinfengZhang
Copy link
Contributor

after #66 & #61 , still 1072 failed tests

@XinfengZhang
Copy link
Contributor

intel/libva-utils#83
this libva-utils issue also caused some failed

@XinfengZhang
Copy link
Contributor

close this issue and trace with new issue #120

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants