Searched refs:failures (Results 1 – 20 of 20) sorted by relevance
342 static int failures = 0; in sha256_self_test() local347 return failures > 0 ? FAIL : OK; in sha256_self_test()371 failures++; in sha256_self_test()376 return failures > 0 ? FAIL : OK; in sha256_self_test()
1 " Test for Vim9 script with failures, causing memory leaks to be reported.
32 to check memory allocation failures are handled gracefully. You need to
45 else ( echo No failures reported > test_result.log )
33 else ( echo No failures reported > test_result.log )
3 " Note: if you get strange failures when adding new tests, it might be that
1120 " Test for various wincmd failures
475 " Memory allocation failures
825 " Test for command failures when the last substitute pattern is not set.
538 " actual failures.
1381 " Tests for failures in the term_dumpwrite() function
1566 " Test for command failures when the last search pattern is not set.
1551 " Tests for memory allocation failures in sign functions
1495 " file present. Next, check for the expected command failures.
57 " highlight the failures
1775 avoiding name conflicts and failures if functionality is added later.
17216 of "-u" to run the script. Fix failures.19429 Solution: Handle failures properly. (Ken Takata)19455 Problem: Build failures on Travis.40737 Problem: MS-Windows: test failures related to VIMDLL.43896 Solution: Add more tests, especially for failures. (Yegappan Lakshmanan,47376 Problem: Vim9: some failures not checked for.49141 Problem: Test failures with legacy Vim script.49318 Problem: Build failures.
7486 Solution: When test.log contains failures exit with non-zero status.
66 Expected test failures:
161 # see all the failures instead of just the first one, but we still want the