Conversation
…ws (paiml/.github) on stock forjar Refs paiml/infra#532
noahgift
added a commit
to paiml/.github
that referenced
this pull request
Sep 23, 2026
…-config, marker, any xml, nextest version) The first real proof run (paiml/forjar#612, run 35886458605) staged 0 junit files. nextest ran the default profile with no fallback, and the warning fired as designed, but it gave no reason. This makes the warning diagnosable. Additive, only on the path that already warns. Refs paiml/infra#532 Pmat-Ticket: PMAT-532 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…r2a-artifact-rows 26ac2cb (junit diagnostic) Refs paiml/infra#532
noahgift
added a commit
to paiml/.github
that referenced
this pull request
Sep 23, 2026
…tored, subshell with a named warning, continue-on-error on every R2a step Proof run 2 (paiml/forjar#612, run 35905480624) went RED because of this workflow change. A scripted edit dropped the backslash from `find … -exec ls {} \;`, find errored ("missing argument to -exec"), and `sh -e` aborted the staging step. That broke the condition this change exists under: nothing here may turn a job red. - the escape is restored (by exact-string edit; the scripted one had eaten it twice); - the diagnostic runs in a subshell whose failure is a NAMED ::warning::, never an abort; - every "Arbiter R2a" step is `continue-on-error: true`: the GitHub-native guarantee that however an R2a step breaks, the job's verdict is the tests', not ours. Verified by extracting the staging step and running it exactly as CI does (`sh -e`): no nextest dir → rc 0 with one warning; a fresh xml → rc 0 and 1 file staged. actionlint findings identical to main. Refs paiml/infra#532 Pmat-Ticket: PMAT-532 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ws 6828e46 (continue-on-error, safe diagnostic) Refs paiml/infra#532
noahgift
added a commit
to paiml/.github
that referenced
this pull request
Sep 24, 2026
…s junit, and print arch, host and cargo's target_directory Proof runs 1-3 on paiml/forjar#612 ran their test jobs on gx10-pool1, yoga-build2 and gx10-pool3, never on intel. The same flag writes junit locally on nextest 0.9.132 and 0.9.143, including with forjar's own nextest.toml. The next run has to say where the file went, or that it was never written. Additive, in the subshell that can never abort the step. Refs paiml/infra#532 Pmat-Ticket: PMAT-532 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…store (.github f1fe394)
… [profile.default.junit] path — the job must be RED and the repo's junit name must win
…overeign-ci (no --tool-config-file) — the control: red without the flag, and no junit artifact
Contributor
Author
|
Closed by the PR-cap triage (paiml/infra#1049). The operator capped open PRs per repo, and this repo is over its cap with no live owning session. The branch is kept, so reopen or fold this into a like PR when work resumes. List and decisions: cop-inbox/evidence/prcap-orphan-triage.md |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Throwaway draft. It points forjar's
cijob atpaiml/.github@arbiter-r2a-artifact-rowsto prove, on real runs, what that workflow change claims (paiml/infra#532, epic paiml/infra#932):junit+sccache-metricsartifacts appear, and pass/fail is unchanged[profile.default.junit]: the repo's file name winsIt gets closed, never merged, when the proofs are recorded.
🤖 Generated with Claude Code