vasilito
cb424d7448
verify-patch-sanity.py validates every active recipe .patch has internally- consistent hunk line counts — catching the 'malformed patch at line N' failure at commit/CI/preflight time instead of hours into a cook. This cycle hit that class three times (qtwaylandscanner, sddm, xwayland), each only discovered when cookbook tried to apply the patch. Running it across the repo found 29 latent malformed patches (validated against GNU patch: e.g. relibc/P3-sysv-ipc reproduces 'malformed patch at line 22'). They were harmless only because they sit in vendored recipes (baked, not re- applied) — but would fail on any version-bump re-derivation. --fix recounts the hunk headers (body untouched) and repaired all 29. Wired into build-preflight.sh (Phase 1.0D) and redbear-ci.yml, with a unit test (test-patch-sanity.sh). Skips archived/legacy trees and unvalidatable formats (empty placeholders, bare-@@ git hunks).
30 lines
1.1 KiB
ReStructuredText
30 lines
1.1 KiB
ReStructuredText
.. _libc_uefi_testing:
|
|
|
|
==========================
|
|
Testing the UEFI C library
|
|
==========================
|
|
|
|
.. contents:: Table of Contents
|
|
:depth: 4
|
|
:local:
|
|
|
|
Testing infrastructure
|
|
======================
|
|
|
|
The LLVM C library supports different kinds of :ref:`tests <build_and_test>`
|
|
depending on the build configuration. The UEFI target is considered a full build
|
|
and therefore provides all of its own utilities to build and run the generated
|
|
tests. Currently UEFI supports two kinds of tests.
|
|
|
|
#. **Hermetic tests** - These are unit tests built with a test suite similar to
|
|
Google's ``gtest`` infrastructure. These use the same infrastructure as unit
|
|
tests except that the entire environment is self-hosted.
|
|
|
|
#. **Integration tests** - These are lightweight tests that simply call a
|
|
``main`` function and checks if it returns non-zero.
|
|
|
|
The UEFI target uses the same testing infrastructure as the other supported
|
|
``libc`` targets. We do this by treating UEFI as a standard hosted environment
|
|
capable of launching a ``main`` function. This only requires us to run the
|
|
tests in a UEFI environment.
|