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).
38 lines
1.2 KiB
ReStructuredText
38 lines
1.2 KiB
ReStructuredText
llvm-test-mustache-spec - LLVM tool to test Mustache library compliance
|
|
=======================================================================
|
|
|
|
.. program:: llvm-test-mustache-spec
|
|
|
|
SYNOPSIS
|
|
--------
|
|
|
|
:program:`llvm-test-mustache-spec` [*inputs...*]
|
|
|
|
Description
|
|
-----------
|
|
|
|
``llvm-test-mustache-spec`` tests the mustache spec conformance of the LLVM
|
|
mustache library. The spec can be found here: https://github.com/mustache/spec
|
|
|
|
To test against the spec, simply download the spec and pass the test JSON files
|
|
to the driver. Each spec file should have a list of tests for compliance with
|
|
the spec. These are loaded as test cases, and rendered with our Mustache
|
|
implementation, which is then compared against the expected output from the
|
|
spec.
|
|
|
|
The current implementation only supports non-optional parts of the spec, so
|
|
we do not expect any of the dynamic-names, inheritance, or lambda tests to
|
|
pass. Additionally, Triple Mustache is not supported. Unsupported tests are
|
|
marked as XFail and are removed from the XFail list as they are fixed.
|
|
|
|
The tool prints the number of test failures and successes in each of the test
|
|
files to standard output.
|
|
|
|
EXAMPLE
|
|
-------
|
|
|
|
.. code-block:: console
|
|
|
|
$ llvm-test-mustache-spec path/to/specs/\*.json
|
|
|