Searched refs:failures (Results 1 – 10 of 10) sorted by relevance
80 int failures = 0; in calloc_self_test() local96 ++failures; in calloc_self_test()113 ++failures; in calloc_self_test()119 ++failures; in calloc_self_test()134 ++failures; in calloc_self_test()150 return( failures ); in calloc_self_test()
45 self.failures = []52 return len(self.successes) + len(self.failures)108 outcomes[key].failures.append(setup)
577 failure_summary_file=$PWD/all-sh-failures-$$.log
96 CF failures by unmarking it. */141 CF failures by unmarking it. */
23 …n existing test case without a good reason. This breaks the tracking of failures across CI runs, s…
85 … trigger by using the API or which cannot be triggered deterministically, for example I/O failures.320 Goal: test the resilience of PSA storage against power failures.
97 * [`test/udp_proxy.c`](test/udp_proxy.c): a UDP proxy that can inject certain failures (delay, dupl…
74 …n (CI) tests are triggered and run. You should follow the result of the CI tests, and fix failures.
392 mbedtls_rsa_rsassa_pss_verify() and was causing failures in some _ALT649 are implemented. This could cause failures or the silent use of non-random714 * Fix build failures on GCC 11. Fixes #3782.1112 failures could happen with alternative implementations of AES. Bug1463 produced by some optimizing compilers, showing up as failures in1712 * Fix build failures on platforms where only gmtime() is available but1980 * Add missing dependencies in test suites that led to build failures2685 * Fix potential build failures related to the 'apidoc' target, introduced2776 * Fix failures in MPI on Sparc(64) due to use of bad assembly code.4202 * All error codes are now negative. Even on mermory failures and IO errors.
249 ### Deprecated error codes for hardware failures were removed664 cause any failures however if you used to enable TLS record-level compression746 to handle failures in the key export callback, for example by
Completed in 19 milliseconds