Searched refs:failures (Results 1 – 6 of 6) sorted by relevance
115 int failures; in main() local119 failures = 0; in main()132 ++failures; in main()136 exit (failures > 0 ? EXIT_FAILURE : EXIT_SUCCESS); in main()
109 static int failures; variable339 ++failures; in f3()341 return failures; in f3()391 ++failures; in f13()393 return failures; in f13()541 ++failures; in f23()543 return failures; in f23()618 ++failures; in f33()620 return failures; in f33()688 ++failures; in test5()[all …]
630 if test "$$xfail" -eq 1; then failures=failure; else failures=failures; fi; \631 banner="$$All$$all $$tests behaved as expected ($$xfail expected $$failures)"; \
139 - Fix a variety of test failures that were due to test fragility rather than486 - Fix inconsequential test failures for hash and SFMT code.807 - Implement atomic operations for x86/x64. This fixes compilation failures828 - Add missing checks for mutex initialization failures.
665 - sem_trywait spurious EAGAIN errors arising from CAS failures1129 - putgrent could write corrupt lines after write failures1267 - getaddrinfo returning EAI_NONAME for some transient failures1407 - multi-threaded set*id() had spurious failures from ugly workaround code
1131 methods that would cause runtime failures. Now trapped as errors are: 1) 2958 invoking these functions caused failures on some machines, probably 7373 input strings could cause unexpected failures if they were shorter than 7703 failures because these fields have meaning in later revisions of the
Completed in 33 milliseconds