Skip to content

armgit / laya

Public Imported from GitHub
0

Non-autoregressive System 1 decision engine. Typed choice, score and yes/no decisions over any text in a single forward pass, in 100+ languages, with a router that picks the right checkpoint per request.

fix(ci): gate Rust skip guard on successful tests

kevin-gatimub10daf497400
diff --git a/.github/workflows/rust.yml b/.github/workflows/rust.yml
index a06b7bf7..a7ff191a 100644
--- a/.github/workflows/rust.yml
+++ b/.github/workflows/rust.yml
@@ -66,7 +66,7 @@ jobs:
set -o pipefail
cargo test --workspace --locked -- --nocapture --test-threads=1 2>&1 | tee cargo-test.log
- name: No test was skipped
- if: ${{ !cancelled() }}
+ if: ${{ success() }}
run: python laya-rust/tools/check_test_skips.py laya-rust/cargo-test.log --min-passed 200
- uses: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02 # v4.6.2
if: ${{ failure() }}
diff --git a/laya-rust/README.md b/laya-rust/README.md
index 4a997bf1..7f8c9b2a 100644
--- a/laya-rust/README.md
+++ b/laya-rust/README.md
@@ -557,6 +557,9 @@ with no path filter. It regenerates fixtures from the Python `laya/` at that com
Goldens are never cached. A `skip:` diagnostic or ignored test makes the lane red, even when
Cargo counts a missing-model early return as a pass. Job-level `continue-on-error` keeps Python
improvements unblocked; Rust drift needs a follow-up port. This workflow never publishes crates.
+The skip guard runs only after successful Cargo tests; regeneration/build failures retain their
+own diagnostics instead of producing a secondary missing-log error.
+
The regeneration self-check compares option logits within `1e-3` and every **unrounded action
softmax probability** within `1e-4`, matching the signal Python and Rust predict consume.
Action classes are not padded option slots and none are excluded. Raw action logits remain