GitHub Actions evidence and interpretation
One-month inventory
| Repository | Runs | Success | Failure | Cancelled |
|---|---|---|---|---|
| syna-isd/biometrics-include | 1 | 1 | 0 | 0 |
| syna-isd/biometrics-sw-niseCore | 46 | 33 | 13 | 0 |
| syna-isd/biometrics-sw-niseWrappers-wbf | 58 | 29 | 29 | 0 |
| syna-isd/sw-driver-biometrics_driver | 184 | 129 | 43 | 12 |
| syna-isd/utest | 70 | 54 | 7 | 9 |
Total: 359 runs—246 success, 92 failure and 21 cancelled. This is an activity inventory, not a release quality percentage: it mixes scheduled production-like workflows, pull requests, development branches, retries and deliberately failing experiments.
Workflow activity
| Repository | Workflow | Runs | Success | Failure | Cancelled |
|---|---|---|---|---|---|
| syna-isd/biometrics-include | Running Copilot Code Review | 1 | 1 | 0 | 0 |
| syna-isd/biometrics-sw-niseCore | Code check | 26 | 16 | 10 | 0 |
| syna-isd/biometrics-sw-niseCore | Dell MIS driver quickbuild | 12 | 9 | 3 | 0 |
| syna-isd/biometrics-sw-niseCore | Running Copilot Code Review | 8 | 8 | 0 | 0 |
| syna-isd/biometrics-sw-niseWrappers-wbf | Code check | 4 | 3 | 1 | 0 |
| syna-isd/biometrics-sw-niseWrappers-wbf | Dell MIS driver quickbuild | 4 | 4 | 0 | 0 |
| syna-isd/biometrics-sw-niseWrappers-wbf | Running Copilot Code Review | 16 | 16 | 0 | 0 |
| syna-isd/biometrics-sw-niseWrappers-wbf | WBF Fingerprint Adapter (C++) | 16 | 3 | 13 | 0 |
| syna-isd/biometrics-sw-niseWrappers-wbf | WBF Fingerprint Adapter (Rust) | 13 | 3 | 10 | 0 |
| syna-isd/biometrics-sw-niseWrappers-wbf | WBFPolicyService Rust | 5 | 0 | 5 | 0 |
| syna-isd/sw-driver-biometrics_driver | .github/workflows/release-all-customers.yml | 1 | 0 | 1 | 0 |
| syna-isd/sw-driver-biometrics_driver | AutoHLK Post Actions | 11 | 11 | 0 | 0 |
| syna-isd/sw-driver-biometrics_driver | Build WBF Driver | 11 | 7 | 3 | 1 |
| syna-isd/sw-driver-biometrics_driver | Daily Release All Customers | 42 | 26 | 12 | 4 |
| syna-isd/sw-driver-biometrics_driver | Daily Release Driver | 2 | 0 | 2 | 0 |
| syna-isd/sw-driver-biometrics_driver | Dispatch IOTA check | 8 | 5 | 3 | 0 |
| syna-isd/sw-driver-biometrics_driver | IOTA Project Rule Check | 65 | 58 | 6 | 1 |
| syna-isd/sw-driver-biometrics_driver | Linux Support Check | 1 | 0 | 0 | 1 |
| syna-isd/sw-driver-biometrics_driver | Manual Trigger AutoHLK | 36 | 15 | 16 | 5 |
| syna-isd/sw-driver-biometrics_driver | Notify IOTA rule changes | 3 | 3 | 0 | 0 |
| syna-isd/sw-driver-biometrics_driver | Running Copilot Code Review | 4 | 4 | 0 | 0 |
| syna-isd/utest | Adapter case-reference freshness | 2 | 0 | 2 | 0 |
| syna-isd/utest | Detect MSFT WBF spec update | 31 | 31 | 0 | 0 |
| syna-isd/utest | Pipeline — extract / build / run (WBF) | 8 | 0 | 5 | 3 |
| syna-isd/utest | Publish integration specs | 2 | 2 | 0 | 0 |
| syna-isd/utest | Virtual test from Markdown (PR) (WBF) (DellMIS) | 11 | 11 | 0 | 0 |
| syna-isd/utest | Virtual test from Markdown (PR) (WBF) (HPCNB) | 9 | 3 | 0 | 6 |
| syna-isd/utest | pages build and deployment | 7 | 7 | 0 | 0 |
Latest concrete validation signals
| Date | Signal | What it proves | What it does not prove |
|---|---|---|---|
| 2026-08-11 | Daily Release All Customers succeeded | Loaded all 13 matrix rows; each check_changes job succeeded; reconciliation succeeded. | Customer build/release jobs were skipped because no relevant source change was detected; this is not a fresh 13-package build. |
| 2026-08-11 | DellMIS virtual test and HPCNB companion succeeded | The selected WBF virtual-test jobs built/ran successfully for their configured test branch. | Other customer branches, hardware, HLK and firmware behavior. |
| 2026-08-10 | Dell WBF quickbuild and code check succeeded | Selected Dell WBF branch passed those workflow checks. | All customer packages or runtime acceptance. |
| 2026-08-10 | Dell niseCore quickbuild and code check succeeded | Selected Dell niseCore branch passed quick build/check after HDRFP-12268 workflow changes. | Full release/sign/HLK coverage. |
| 2026-08-10 | Feature-branch Build WBF Driver succeeded after two failed attempts | The build job—including the composite build/validate/sign/upload step—completed for that feature-branch input. | Every customer or scheduled release health. |
| 2026-08-03 | Rust adapter and C++ adapter succeeded | Their integration-test workflows passed at the tested Rust-branch revision. | Full behavioral parity, hardware behavior or all customer configurations. |
| 2026-08-11 | IOTA Project Rule Check succeeded on master | Configured IOTA project rules passed that run. | Firmware-side interpretation or every device update path. |
How failures are used
- A failed run is operational evidence tied to a run ID, branch, head SHA, attempt, failed job/step and time.
- Repeated failures followed by success reveal development convergence; they should not be deleted from project history.
- Cancelled runs are neither pass nor fail unless cancellation policy proves supersession.
- Skipped jobs must be shown explicitly. A successful orchestrator with skipped build jobs does not prove the package builds.
- Jira state remains independent. For example, HDRFP-12268 is still In Progress even though Jira links three merged PRs/six successful builds and the latest quickbuild workflows succeeded.
Recommended recurring record
For each semantically important run retain: repository/workflow/run ID, event, branch/head SHA, attempt, conclusion, job/step scope, artifact or report URL, linked Jira/commit, and whether it is unit, virtual, build, signing, package, HLK, IOTA or release evidence.