Searched refs:failures (Results 1 – 17 of 17) sorted by relevance
| /mbedtls-3.7.0/tests/scripts/ |
| D | run_demos.py | 23 failures = []
29 failures.append(demo)
36 successes = len(demos) - len(failures)
38 if failures and not quiet:
39 print('Failures:', *failures)
40 return not failures
|
| D | depends.py | 467 failures = []
477 failures.append(job.name)
492 if failures:
493 log_line('{} FAILED'.format(' '.join(failures)), color=colors.bold_red)
|
| D | analyze_outcomes.py | 91 suite_case in comp_outcomes.failures
183 outcomes[component].failures.add(suite_case)
|
| D | all.sh | 626 failure_summary_file=$PWD/all-sh-failures-$$.log
|
| /mbedtls-3.7.0/programs/test/ |
| D | selftest.c | 57 int failures = 0; in calloc_self_test() local
75 ++failures; in calloc_self_test()
100 ++failures; in calloc_self_test()
116 ++failures; in calloc_self_test()
121 ++failures; in calloc_self_test()
135 ++failures; in calloc_self_test()
144 ++failures; in calloc_self_test()
155 ++failures; in calloc_self_test()
173 return failures; in calloc_self_test()
|
| /mbedtls-3.7.0/tests/suites/ |
| D | test_suite_base64.function | 76 CF failures by unmarking it. */
119 CF failures by unmarking it. */
|
| D | test_suite_platform.function | 91 * The test often failed on the CI. See #1517. CI failures cannot be
|
| D | test_suite_psa_crypto_pake.function | 566 * This check is used for failures that are injected at code level. There's only
|
| /mbedtls-3.7.0/docs/architecture/testing/ |
| D | test-framework.md | 23 …n existing test case without a good reason. This breaks the tracking of failures across CI runs, s…
|
| D | invasive-testing.md | 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.
|
| /mbedtls-3.7.0/programs/ |
| D | README.md | 97 * [`test/udp_proxy.c`](test/udp_proxy.c): a UDP proxy that can inject certain failures (delay, dupl…
|
| /mbedtls-3.7.0/ |
| D | CONTRIBUTING.md | 70 …n (CI) tests are triggered and run. You should follow the result of the CI tests, and fix failures.
|
| D | ChangeLog | 186 which mainly causes failures when building Windows target using
582 * Update test data to avoid failures of unit tests after 2023-08-07.
1166 * Fix several bugs (warnings, compiler and linker errors, test failures)
1376 * Some failures of HMAC operations were ignored. These failures could only
1843 mbedtls_rsa_rsassa_pss_verify() and was causing failures in some _ALT
2100 are implemented. This could cause failures or the silent use of non-random
2165 * Fix build failures on GCC 11. Fixes #3782.
2563 failures could happen with alternative implementations of AES. Bug
2914 produced by some optimizing compilers, showing up as failures in
3163 * Fix build failures on platforms where only gmtime() is available but
[all …]
|
| /mbedtls-3.7.0/docs/ |
| D | 3.0-migration-guide.md | 270 ### Deprecated error codes for hardware failures were removed
692 cause any failures however if you used to enable TLS record-level compression
774 to handle failures in the key export callback, for example by
|
| /mbedtls-3.7.0/docs/architecture/psa-thread-safety/ |
| D | psa-thread-safety.md | 67 > The consistency requirement does not apply to errors that arise from resource failures or limitat…
244 …PSA_SLOT_PENDING_DELETION` meaning that the key has been destroyed. For failures, the linearizatio…
|
| /mbedtls-3.7.0/docs/architecture/ |
| D | psa-storage-resilience.md | 105 We assume that power failures are rare. Therefore we will primarily optimize for the normal case. T…
294 … is maintained. No modification of normal behavior (such as simulated power failures) is necessary.
|
| D | psa-shared-memory.md | 178 …am, with no error condition detected after setup other than operational failures (e.g. communicati…
685 …ograms/test/metatest.c`, which is a program designed to check that test failures happen correctly.…
|
