| #
39846d56 |
| 05-Mar-2024 |
Robin Jarry <rjarry@redhat.com> |
test: assume C source files are UTF-8 encoded
Instead of relying on the default locale from the environment (LC_ALL),
explicitly read the files as utf-8 encoded.
Fixes: 0aeaf75df879 ("test: define
test: assume C source files are UTF-8 encoded
Instead of relying on the default locale from the environment (LC_ALL),
explicitly read the files as utf-8 encoded.
Fixes: 0aeaf75df879 ("test: define unit tests suites based on test types")
Cc: stable@dpdk.org
Signed-off-by: Robin Jarry <rjarry@redhat.com>
Acked-by: Bruce Richardson <bruce.richardson@intel.com>
Acked-by: Morten Brørup <mb@smartsharesystems.com>
Acked-by: Tyler Retzlaff <roretzla@linux.microsoft.com>
show more ...
|
| #
25065ef1 |
| 15-Sep-2023 |
Bruce Richardson <bruce.richardson@intel.com> |
test: emit warning for orphaned tests
When doing a scan for tests to add to test suites, we can also detect
the tests which have not been added to any suite. By doing so:
a) we can emit a warning i
test: emit warning for orphaned tests
When doing a scan for tests to add to test suites, we can also detect
the tests which have not been added to any suite. By doing so:
a) we can emit a warning informing the developer that the test is not in
a suite (if developer mode is enabled)
b) we can still register a test for that command making these tests
callable through "meson test"
Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
Reviewed-by: David Marchand <david.marchand@redhat.com>
show more ...
|
| #
0aeaf75d |
| 16-Aug-2023 |
Bruce Richardson <bruce.richardson@intel.com> |
test: define unit tests suites based on test types
Rather than having the test suites listed out in the meson.build files
and having to have them enabled/disabled selectively based on what libs
are
test: define unit tests suites based on test types
Rather than having the test suites listed out in the meson.build files
and having to have them enabled/disabled selectively based on what libs
are being built, pull the tests to run from the source files which were
added to the build.
Most test suites require no additional info other than the list of test
names in the suite. However the fast-test are special that they have
additional parameters associated with them. This requires some
additional work in the test extraction script and in the meson.build
file for processing the output.
Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
Acked-by: Morten Brørup <mb@smartsharesystems.com>
show more ...
|