modelcontextprotocol/conformance
Watch
1
0
Fork
You've already forked conformance
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

ci(traceability): tolerate SDK conformance failures in the run step (#290)

Browse source 
The `sdk` command exits non-zero when the SDK has conformance failures
not in its baseline. The traceability manifest only needs the emitted
check IDs (written regardless of pass/fail), so a failing SDK must not
fail the refresh. Add `|| true`; the existing 'no results produced'
guard catches a genuinely broken run.
This commit is contained in:
Paul Carleton 2026-05-19 23:06:39 +01:00 • committed by GitHub
commit e5afe404ad
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 5 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

7
.github/workflows/traceability.yml vendored
View file

@ -52,9 +52,12 @@ jobs:
- name: Run conformance suites against the reference SDK
# `sdk` requires --mode client|server; run both into the same results dir
# (the second reuses the cached checkout + build via --skip-build).
# `|| true`: the manifest only needs the emitted check IDs (written
# regardless of pass/fail), so SDK conformance failures must not fail
# this step. The "no results produced" guard below is the real safety net.
run: |
node dist/index.js sdk "$SDK_REF" --mode client --suite all -o results
node dist/index.js sdk "$SDK_REF" --mode server --suite all --skip-build -o results
node dist/index.js sdk "$SDK_REF" --mode client --suite all -o results || true
node dist/index.js sdk "$SDK_REF" --mode server --suite all --skip-build -o results || true
- name: Fail if no results were produced
run: |