morluto/rea

Fork 0

mirror of https://github.com/morluto/rea.git synced 2026-11-05 06:45:22 +00:00

[GH-ISSUE #8618] [Bug] Direct inspector observation fails without diagnostic in CI #7497

New issue

Open

opened 2026-11-03 00:30:13 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-11-03 00:30:13 +00:00

Owner

Originally created by @morluto on GitHub (Nov 2, 2026).
Original GitHub issue: https://github.com/morluto/rea/issues/8618

Before submitting

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

Area

Process capture or runtime observation

Observed behavior

In CI shard 7 for PR #8613, tests/boundary/mcp/javascriptRuntimeObservationMcp.test.ts failed in lists and observes one target as retained Evidence: the second, direct observation returned ok: false after the MCP observation had succeeded. The assertion printed only expected false to be true, not the typed error. The PR does not change this test or the inspector provider.

Reproduction

Observed once in the linked Linux CI shard at PR head ae8223ccdfa0d5dbc659ddcbb7d6acf360343c3f. On macOS arm64 with Node 24.22.1 at that head, npm run test:focused -- tests/boundary/mcp/javascriptRuntimeObservationMcp.test.ts passed all three tests once. A deterministic reproduction and failure frequency are unknown.

Expected behavior

The direct observation of the fake inspector should succeed and produce the same Evidence ID as the preceding MCP observation; if it fails, the test output should preserve the actual typed failure to permit diagnosis.

Impact and scope

One CI shard failed and other shards were cancelled. Whether this reflects a product failure, fixture lifecycle, timing, or environment is unknown. No production runtime or real V8 inspector failure was observed.

REA version

ae8223ccdfa0d5dbc659ddcbb7d6acf360343c3f.

Runtime and platform

CI: Linux, Node 24.22.1; exact runner details are in the linked job. Local control: macOS arm64, Node 24.22.1.

Target and artifact context

Test-owned fake V8 inspector and temporary JavaScript entry file; no real target attached.

Interface

MCP

Earliest failure stage

Unknown

Relevant output or evidence

The linked job shows the failure at line 292: expect(direct.ok).toBe(true) received false. The actual Result error is not printed. The same job reports 210 test files passed and one failed. Source tests in the same run passed.

Analysis or suspected cause

NOT_ENOUGH_INFO: the failure result was not captured, so a root cause and any connection to PR #8613 remain unestablished. A useful next check is to expose the typed error at the assertion, then reproduce with the CI fixture and workload before changing timeouts or behavior.

cc @gensokyo-dev @kaoru0822-kitauji @N0zoM1z0

Originally created by @morluto on GitHub (Nov 2, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/8618 ### Before submitting - [x] I searched the open and closed issues for a related report. - [x] I removed credentials, tokens, private paths, and sensitive target data. ### Area Process capture or runtime observation ### Observed behavior In [CI shard 7 for PR #8613](https://github.com/morluto/rea/actions/runs/41379843276/job/125068368043), `tests/boundary/mcp/javascriptRuntimeObservationMcp.test.ts` failed in `lists and observes one target as retained Evidence`: the second, direct observation returned `ok: false` after the MCP observation had succeeded. The assertion printed only `expected false to be true`, not the typed error. The PR does not change this test or the inspector provider. ### Reproduction Observed once in the linked Linux CI shard at PR head `ae8223ccdfa0d5dbc659ddcbb7d6acf360343c3f`. On macOS arm64 with Node 24.22.1 at that head, `npm run test:focused -- tests/boundary/mcp/javascriptRuntimeObservationMcp.test.ts` passed all three tests once. A deterministic reproduction and failure frequency are unknown. ### Expected behavior The direct observation of the fake inspector should succeed and produce the same Evidence ID as the preceding MCP observation; if it fails, the test output should preserve the actual typed failure to permit diagnosis. ### Impact and scope One CI shard failed and other shards were cancelled. Whether this reflects a product failure, fixture lifecycle, timing, or environment is unknown. No production runtime or real V8 inspector failure was observed. ### REA version `ae8223ccdfa0d5dbc659ddcbb7d6acf360343c3f`. ### Runtime and platform CI: Linux, Node 24.22.1; exact runner details are in the linked job. Local control: macOS arm64, Node 24.22.1. ### Target and artifact context Test-owned fake V8 inspector and temporary JavaScript entry file; no real target attached. ### Interface MCP ### Earliest failure stage Unknown ### Relevant output or evidence The linked job shows the failure at line 292: `expect(direct.ok).toBe(true)` received false. The actual `Result` error is not printed. The same job reports 210 test files passed and one failed. Source tests in the same run passed. ### Analysis or suspected cause NOT_ENOUGH_INFO: the failure result was not captured, so a root cause and any connection to PR #8613 remain unestablished. A useful next check is to expose the typed error at the assertion, then reproduce with the CI fixture and workload before changing timeouts or behavior. cc @gensokyo-dev @kaoru0822-kitauji @N0zoM1z0

bsakaguchi added the

bug

triage

labels

2026-11-03 00:30:13 +00:00

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

morluto/rea#7497

No description provided.

Rows
Columns