[PATCH uci 4/6] tests: cram: add uci import testing on fuzzer corpus
Hauke Mehrtens
hauke at hauke-m.de
Sun Oct 4 11:10:59 EDT 2020
On 10/3/20 9:48 AM, Petr Štetiar wrote:
> Use valgrind and uci cli compiled with undefined, address and leak
> sanitizers.
....
> diff --git a/tests/cram/test-san_uci_import.t b/tests/cram/test-san_uci_import.t
> new file mode 100644
> index 000000000000..7faed221f93e
> --- /dev/null
> +++ b/tests/cram/test-san_uci_import.t
> @@ -0,0 +1,15 @@
> +check that uci import is producing expected results:
> +
> + $ [ -n "$BUILD_BIN_DIR" ] && export PATH="$BUILD_BIN_DIR:$PATH"
> + $ export TEST_INPUTS="$TESTDIR/inputs"
> + $ export FUZZ_CORPUS="$TESTDIR/../fuzz/corpus"
> +
> + $ for file in $(LC_ALL=C find $FUZZ_CORPUS -type f | sort ); do
> + > uci-san import -f $file; \
> + > done
> + uci-san: I/O error
> + uci-san: Parse error (invalid command) at line 0, byte 0
> + uci-san: Parse error (invalid command) at line 1, byte 18
I do not get this error. Which test case should trigger it?
> + uci-san: I/O error
> + uci-san: I/O error
> + [1].....
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://lists.openwrt.org/pipermail/openwrt-devel/attachments/20201004/97d676f9/attachment-0001.sig>
More information about the openwrt-devel
mailing list