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).
27 lines
1.2 KiB
ReStructuredText
27 lines
1.2 KiB
ReStructuredText
Conformance Testing
|
|
===================
|
|
|
|
Mesa as a project does not get certified conformant by Khronos for the
|
|
APIs it implements. Rather, individual driver teams run the
|
|
conformance tests and submit their results on a set of hardware on a
|
|
particular operating system. The canonical list is at Khronos' list
|
|
of `conformant
|
|
products <https://www.khronos.org/conformance/adopters/conformant-products/>`_
|
|
and you can find some reports there by searching for "Mesa",
|
|
"Raspbian" and "RADV" for example.
|
|
|
|
Submitting conformance results to Khronos
|
|
-----------------------------------------
|
|
|
|
If your driver team is associated with an organization that is a
|
|
Khronos member and has submitted conformance for your API on another
|
|
software stack (likely you're a hardware company), it will probably be
|
|
easiest to submit your conformance through them.
|
|
|
|
If you are an individual developer or your organization hasn't
|
|
submitted results for the given API yet, X.Org is a member through
|
|
the Software Freedom Conservancy, and they can help submit your
|
|
conformance results to get added to the list of conformant products.
|
|
You should probably coordinate with board@foundation.x.org for your
|
|
first submission.
|