@sreetej510/pi-shipd-checks 0.10.9 → 0.10.10
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +1 -1
- package/dist/fargate-worker.mjs +348 -348
- package/dist/index.js +1 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -175,7 +175,7 @@ enabled project list is stored alongside the other settings in `~/.pi/agent/chec
|
|
|
175
175
|
|
|
176
176
|
The patch precheck always uses the `medium` Fargate profile. It applies `test.patch`, creates isolated workspaces with and without `solution.patch`, and runs the base suites concurrently in both workspaces followed by the new suites concurrently in both workspaces. It requires
|
|
177
177
|
`./test.sh base` to pass, requires every `./test.sh new` testcase to fail or error individually (with no suite-level error)
|
|
178
|
-
before `solution.patch`, then requires both base and new suites to pass after the solution patch. A failed precheck aborts
|
|
178
|
+
before `solution.patch`, then requires both base and new suites to pass after the solution patch. Pytest subtest totals are not treated as passing testcase records; emitted `<testcase>` statuses and explicit `SUBPASSED` records are used for the pre-solution invariant. A failed precheck aborts
|
|
179
179
|
before Shipd is opened and includes the Linux platform, a human-readable phase, and failed/errored test names in the tool error.
|
|
180
180
|
|
|
181
181
|
The `gap-finder` and `solution-precheck` tools are read-only and return repair recommendations; the caller changes the
|