PCI VPD: Fix a wrong return code in a test case

The test case should return -1, not 0 in case a valid resource could
not be parsed successfully but the ret value is initialized to 0.

Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
Signed-off-by: Dmitrii Shcherbakov <dmitrii.shcherbakov@canonical.com>

diff --git a/tests/virpcivpdtest.c b/tests/virpcivpdtest.c
index b7bc86d92297d673f0cb62f43f9fbe1afa101f2f..a9405f94276841b2a086e0bfb7379cea6c4b2da2 100644 (file)
--- a/tests/virpcivpdtest.c
+++ b/tests/virpcivpdtest.c
@@ -537,7 +537,6 @@ testVirPCIVPDParseFullVPD(const void *opaque G_GNUC_UNUSED)
 {
     int fd = -1;
     size_t dataLen = 0;
-    int ret = 0;
 
     g_autoptr(virPCIVPDResource) res = NULL;
     /* Note: Custom fields are supposed to be freed by the resource cleanup code. */
@@ -558,7 +557,7 @@ testVirPCIVPDParseFullVPD(const void *opaque G_GNUC_UNUSED)
     if (!res) {
         virReportError(VIR_ERR_INTERNAL_ERROR, "%s",
                        "The resource pointer is NULL after parsing which is unexpected");
-        return ret;
+        return -1;
     }
 
     if (!res->ro) {
@@ -596,7 +595,7 @@ testVirPCIVPDParseFullVPD(const void *opaque G_GNUC_UNUSED)
         return -1;
 
     custom = NULL;
-    return ret;
+    return 0;
 }
 
 static int