[GH-ISSUE #1001] [Bug] CI test shards omit the build-generated source catalog #375

New issue

Closed

opened 2026-10-15 18:24:24 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-15 18:24:24 +00:00

Owner

Originally created by @N0zoM1z0 on GitHub (Oct 7, 2026).
Original GitHub issue: https://github.com/morluto/rea/issues/1001

Before submitting

I searched open and closed issues for a related report.
I removed credentials, tokens, private paths, and sensitive target data.

Area

Setup, packaging, or upgrade (CI test prerequisites).

Observed behavior

After #997 made src/generatedMcpToolCatalog.ts build-generated and gitignored, CI test shards 1 and 3 fail to import it. The shard jobs download only rea-dist and invoke test:ci:shard:run, which intentionally skips the build. The aggregate coverage job consequently fails.

Observed in shard 1 and shard 3. The separate snapshot fixture regression passed; these failures occur during test module loading.

Reproduction

Use a clean checkout after #997 and run npm ci.
Download the matching rea-dist artifact into dist, as .github/workflows/ci.yml does for each shard.
Run the acceptance/auxiliary-provider/MCP catalog suites through test:ci:shard:run without a local build.
Observe missing generated source imports.

Expected behavior

Each shard should prepare the generated source catalog from the downloaded build before loading source tests. Preserve shared build reuse without recompiling REA in every shard.

Impact and scope

Deterministic CI catalog acceptance, auxiliary-provider and SDK registration/schema suites cannot load. This blocks meaningful complete coverage results. The observed failure does not establish a runtime provider or hash regression.

REA version

PR #999 head dba612a3, tested against main containing #997 and #998; current main 06b047a0 retains the same shard prerequisite gap.

Runtime and platform

GitHub-hosted Ubuntu x64, Node selected by .nvmrc.

Target and artifact context

Source test catalog and downloaded REA build artifact.

Interface

Other (GitHub Actions deterministic test lane).

Earliest failure stage

Setup or provider admission (test module loading).

Relevant output or evidence

Cannot find module '../../src/generatedMcpToolCatalog.js'

Affected suites: contractPresentation, auxiliaryDeclarations, toolRegistrationOptions, and toolSchemaValidity.

Analysis or suspected cause

Source-derived: the build now generates the source catalog, but the rea-dist artifact uploads only dist. Shard jobs neither run the build nor generate this source prerequisite. Run the existing catalog generator immediately after downloading the matching build and before loading shard tests.

Additional context

This is separate from the transient MinGW download timeout observed on #988, which passed on retry without a CI configuration change.

Originally created by @N0zoM1z0 on GitHub (Oct 7, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/1001 ## Before submitting - [x] I searched open and closed issues for a related report. - [x] I removed credentials, tokens, private paths, and sensitive target data. ## Area Setup, packaging, or upgrade (CI test prerequisites). ## Observed behavior After #997 made `src/generatedMcpToolCatalog.ts` build-generated and gitignored, CI test shards 1 and 3 fail to import it. The shard jobs download only `rea-dist` and invoke `test:ci:shard:run`, which intentionally skips the build. The aggregate coverage job consequently fails. Observed in [shard 1](https://github.com/morluto/rea/actions/runs/37651521680/job/112896128879) and [shard 3](https://github.com/morluto/rea/actions/runs/37651521680/job/112896129098). The separate snapshot fixture regression passed; these failures occur during test module loading. ## Reproduction 1. Use a clean checkout after #997 and run `npm ci`. 2. Download the matching `rea-dist` artifact into `dist`, as `.github/workflows/ci.yml` does for each shard. 3. Run the acceptance/auxiliary-provider/MCP catalog suites through `test:ci:shard:run` without a local build. 4. Observe missing generated source imports. ## Expected behavior Each shard should prepare the generated source catalog from the downloaded build before loading source tests. Preserve shared build reuse without recompiling REA in every shard. ## Impact and scope Deterministic CI catalog acceptance, auxiliary-provider and SDK registration/schema suites cannot load. This blocks meaningful complete coverage results. The observed failure does not establish a runtime provider or hash regression. ## REA version PR #999 head `dba612a3`, tested against main containing #997 and #998; current main `06b047a0` retains the same shard prerequisite gap. ## Runtime and platform GitHub-hosted Ubuntu x64, Node selected by `.nvmrc`. ## Target and artifact context Source test catalog and downloaded REA build artifact. ## Interface Other (GitHub Actions deterministic test lane). ## Earliest failure stage Setup or provider admission (test module loading). ## Relevant output or evidence ```text Cannot find module '../../src/generatedMcpToolCatalog.js' ``` Affected suites: `contractPresentation`, `auxiliaryDeclarations`, `toolRegistrationOptions`, and `toolSchemaValidity`. ## Analysis or suspected cause Source-derived: the build now generates the source catalog, but the `rea-dist` artifact uploads only `dist`. Shard jobs neither run the build nor generate this source prerequisite. Run the existing catalog generator immediately after downloading the matching build and before loading shard tests. ## Additional context This is separate from the transient MinGW download timeout observed on #988, which passed on retry without a CI configuration change.

bsakaguchi

2026-10-15 18:24:24 +00:00