The only diffs are:
- The non-compatibility version relies on the queue being in-order
to remove one explicit dependency. This isn't directly related
to the functionality under test.
- A memory leak was fixed in the non-compatibility suite
Signed-off-by: Kevin Petit <kevin.petit@arm.com>
The only diffs are:
- obvious bug fixes in the non-compatibility suite
- use of 2.x vs 1.x device properties (now covered by compatibility
query tests in the non-compatibility suites)
- additional requirements for 2.x features in the non-compatibility
suite (gated by a version check so looks like it would work as is
on a 1.x implemenmtation)
Signed-off-by: Kevin Petit <kevin.petit@arm.com>
...and mark tests that exercise new-style entrypoints as requiring 2.0
These tests give us (or rather will give us once made exhaustive, see
#508) coverage for both new-style and old-style creation entrypoints,
making the entrypoint used in other tests irrelevant as long as the
old-style entrypoints are required to be implemented.
Signed-off-by: Kévin Petit <kpet@free.fr>
As agreed in the WG calls, the query tests are sufficient to cover
both old-style and new-style sampler and command queue creation
entrypoints.
Use old-style entrypoints in all tests that don't require 2.x
features to get compatibility with 1.x implementations.
This makes it possible to remove duplicate compatibility tests.
Contributes to #494.
Signed-off-by: Kévin Petit <kpet@free.fr>
- whitespace diffs
- trivial differences (mostly bugfixes merged to master)
- use of the kernel helpers to create programs
Signed-off-by: Kévin Petit <kpet@free.fr>
Use the non-compatibility version.
In each case the diff was minimal, didn't have modifications that
would invalidate compatibility testing and it was clear that the
"latest/best" version was not the one in the compatibility copy.
Signed-off-by: Kevin Petit <kevin.petit@arm.com>
This removes all the duplicated code from each test, and moves it to
test harness so that we have single place where this information is
printed.
Signed-off-by: Radek Szymanski <radek.szymanski@arm.com>
The test has been ignoring potential failures in memory allocations,
giving misleading error messages.
Add a simple check and return early if the allocation failed.
Signed-off-by: Radek Szymanski <radek.szymanski@arm.com>
This was causing some tests to fail on 2.1 conformance
with : device version string does not match required format!
Signed-off-by: Oualid Khelifi <oualid.khelifi@arm.com>
This adds functionality to define minimal required version through the
ADD_TEST* macros. Tests that don't meet the version requirement will
be skipped.
By default the minimal required version is set to 1.0, subsequent
patches will set the appropriate version for each of the tests.
Signed-off-by: Radek Szymanski <radek.szymanski@arm.com>
This adds functionality to define minimal required version through the
ADD_TEST* macros. Tests that don't meet the version requirement will
be skipped.
By default the minimal required version is set to 1.0, subsequent
patches will set the appropriate version for each of the tests.
Signed-off-by: Radek Szymanski <radek.szymanski@arm.com>
This moves from numeric values to enum values to keep result state of
the test, so we can easily save this information in JSON results.
Signed-off-by: Radek Szymanski <radek.szymanski@arm.com>
This moves from numeric values to enum values to keep result state of
the test, so we can easily save this information in JSON results.
Signed-off-by: Radek Szymanski <radek.szymanski@arm.com>
The maintenance of the conformance tests is moving to Github.
This commit contains all the changes that have been done in
Gitlab since the first public release of the conformance tests.
Signed-off-by: Kevin Petit kevin.petit@arm.com
The maintenance of the conformance tests is moving to Github.
This commit contains all the changes that have been done in
Gitlab since the first public release of the conformance tests.
Signed-off-by: Kevin Petit <kevin.petit@arm.com>
