test/compress: clarify out-of-space error messages
authorFiona Trahe <fiona.trahe@intel.com>
Fri, 5 Jul 2019 17:19:10 +0000 (18:19 +0100)
committerAkhil Goyal <akhil.goyal@nxp.com>
Fri, 19 Jul 2019 12:15:21 +0000 (14:15 +0200)
Use ERR rather than INFO to warn that it's a negative test else
the errors are seen but the warning to expect them isn't.
Also add comment to make it easier to follow code.

Signed-off-by: Fiona Trahe <fiona.trahe@intel.com>
Acked-by: Adam Dybkowski <adamx.dybkowski@intel.com>
app/test/test_compressdev.c

index cf78775..65889c2 100644 (file)
@@ -1870,7 +1870,7 @@ test_compressdev_out_of_space_buffer(void)
        uint16_t i;
        const struct rte_compressdev_capabilities *capab;
 
-       RTE_LOG(INFO, USER1, "This is a negative test errors are expected\n");
+       RTE_LOG(ERR, USER1, "This is a negative test errors are expected\n");
 
        capab = rte_compressdev_capability_get(0, RTE_COMP_ALGO_DEFLATE);
        TEST_ASSERT(capab != NULL, "Failed to retrieve device capabilities");
@@ -1901,7 +1901,7 @@ test_compressdev_out_of_space_buffer(void)
                RTE_COMP_OP_STATELESS,
                LB_BOTH,
                ZLIB_DECOMPRESS,
-               1,
+               1,  /* run out-of-space test */
                0
        };
        /* Compress with compressdev, decompress with Zlib */