12 Oct
2017
12 Oct
'17
4:19 p.m.
On 10/04/2017 10:58 AM, Jiri Denemark wrote:
If the actual result does not match our expectation, the tests would not correctly show the difference if a CPU feature is disabled in the expected result and the actual result does not mention it at all. The test could complain about an unrelated CPU feature or it could even crash in case the actual result contains no more features to go through.
Signed-off-by: Jiri Denemark <jdenemar@redhat.com> --- tests/cputest.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
I recognize this - it was something I noted at one time from a Coverity test failure... Reviewed-by: John Ferlan <jferlan@redhat.com> John