Compare commits

...
Author SHA1 Message Date
N0zoM1z0andKaoru0822 a13200b01d chore(ci): inspect structured Windows baseline spawn failures
The JSON reporter retains original errors in failureMessages but suppresses captured console output. Use unmodified baseline source and require both exact spawn failures before checking the candidate.

Co-authored-by: Kaoru0822 <208281322+kaoru0822-kitauji@users.noreply.github.com>
2026-10-15 15:33:21 +00:00
N0zoM1z0andKaoru0822 f3d4abd3eb chore(ci): run isolated native Windows Evidence transport proof
Verification-only branch; do not integrate the diagnostic workflow.

Co-authored-by: Kaoru0822 <208281322+kaoru0822-kitauji@users.noreply.github.com>
2026-10-15 15:29:32 +00:00
N0zoM1z0andKaoru0822 8809be9343 test(applications): reuse owned files for complete Evidence requests
Refresh the Windows request transport fix onto current main. Keep the already-file-backed rest trace unchanged and reuse each existing test-owned directory for the remaining two complete Evidence requests.

Co-authored-by: Kaoru0822 <208281322+kaoru0822-kitauji@users.noreply.github.com>
2026-10-15 15:28:45 +00:00
Kaoru0822 3789d31e25 Merge remote-tracking branch 'origin/main' into HEAD
# Conflicts:
#	tests/acceptance/applications/applicationWorkflowCli.test.ts
2026-10-14 05:14:49 +00:00
GuilhermeF 7628b0ad89 test(applications): pass Evidence requests to the CLI through files
Three application workflow CLI acceptance tests serialized complete
Evidence documents into one process argument. On Windows the command line
exceeds the process limit, so execFile rejects the spawn with
ENAMETOOLONG before the semantic trace or export-shape comparison starts.

Write those requests to a JSON file owned by the test case and pass its
path, which the CLI already accepts through the shared JSON input
boundary. Evidence stays complete; inline JSON transport keeps its
coverage in the existing parity and malformed-input tests.

Fixes #2942
2026-10-13 20:44:26 -03:00
2 changed files with 104 additions and 928 deletions

No files matched your search

+78 -918
View File
File diff suppressed because it is too large. Load diff
@@ -850,18 +850,18 @@ describe("application workflow CLI parity", () => {
if (seed === undefined)
throw new TypeError("Expected at least one semantic relation");
const traced = await runCli([
const traced = await runCliWithRequestFile(
root,
"trace-javascript-semantics",
JSON.stringify({
{
application: analyzed.value,
query: {
seed: { kind: "semantic-node", node_id: seed },
direction: "forward-influence",
include_ambiguous_dynamic_edges: true,
},
}),
"--json",
]);
},
);
expect(traced).toMatchObject({
operation: "trace_javascript_semantics",
predicate_type: "rea.javascript-semantic-trace",
@@ -1300,18 +1300,18 @@ describe("application workflow CLI export Evidence", () => {
'export default async function make() { return { kind: "record", extra: 1 }; }',
];
const [left, right] = await analyzeComparisonSources(root, sources);
const compared = await runCli([
const compared = await runCliWithRequestFile(
root,
"compare-javascript-export-shapes",
JSON.stringify({
{
left,
right,
left_module_path: "parser.mjs",
left_export_name: "default",
right_module_path: "parser.mjs",
right_export_name: "default",
}),
"--json",
]);
},
);
expect(compared).toMatchObject({
operation: "compare_javascript_export_shapes",
normalized_result: {
@@ -1640,3 +1640,19 @@ const runCli = async (
throw cause;
}
};
/**
* Pass a request carrying complete Evidence through the CLI's file-backed JSON
* input. Serialized Evidence exceeds the Windows command-line limit when it is
* passed as one argument, so spawn fails with ENAMETOOLONG before the workflow
* starts. Inline JSON transport keeps its own coverage in the parity tests.
*/
const runCliWithRequestFile = async (
root: string,
command: string,
request: unknown,
): Promise<unknown> => {
const requestPath = join(root, "request.json");
await writeFile(requestPath, JSON.stringify(request));
return runCli([command, requestPath, "--json"]);
};