Unit testing: solvers and their kernels

[shurale-nkn]

As part of improving the testing system and expanding the developer tools.
Required to be able to test each solver and each of its unique combinations of kernels, directly and in different testing modes.

Goals:

• Exclude the influence of errors in the control logic(search, find, tuning, database operations) on the result of verification of the developed solutions.
• Exclude the possibility of negative impact on the system from slow solutions, because they will be executed at the search stage. (Add the ability to test all algorithms, solvers, and kernels, not only fastest one.)
• Add the ability to test solutions in different modes:
  • BitExact verification mode.
  • Сhecking segfaults. Checks that the kernel is not trying to read or write an illegal memory location.
  • Solver API testing.

Opportunities:

• Reduce testing time. Solver testing should be restarted only if its files have been modified.
• Improve testing coverage.
• Tested GPU solutions can prepare gold output results instead of CPU. (Reduce verification time)

[shurale-nkn]

FYI @Kirpich30000

[atamazov]

Related ticket: https://github.com/AMDComputeLibraries/MLOpen/issues/2212.

[ppanchad-amd]

@shurale-nkn Please try latest ROCm 6.0.2 to see if your issue still occurs? Please close ticket if this is no longer an issue. Thanks.