Skip to content

chore: mcp-inspector docs #1396

chore: mcp-inspector docs

chore: mcp-inspector docs #1396

Triggered via push March 4, 2026 17:21
Status Success
Total duration 18m 0s
Artifacts

test.yml

on: push
yarn-lockfile-check  /  lockfile-check
8s
yarn-lockfile-check / lockfile-check
Matrix: e2e
linux-unit-tests  /  determine-node-versions
7s
linux-unit-tests / determine-node-versions
Matrix: linux-unit-tests / linux-unit-tests
windows-unit-tests  /  determine-node-versions
8s
windows-unit-tests / determine-node-versions
Matrix: windows-unit-tests / windows-unit-tests
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 1 warning
test/actions/run-analyzer.test.ts > RunAnalyzerActionImpl > When 'no violations are found and all engin…', 'the status is "success" and the outfi…': packages/mcp-provider-code-analyzer/test/actions/run-analyzer.test.ts#L197
Error: Test timed out in 60000ms. If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout". ❯ test/actions/run-analyzer.test.ts:197:6
test/actions/describe-rule.test.ts > DescribeRuleActionImpl > 'When a custom configuration is presen…' > When asked to describe an existing rule, the correct description is returned: packages/mcp-provider-code-analyzer/test/actions/describe-rule.test.ts#L47
Error: Test timed out in 60000ms. If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout". ❯ test/actions/describe-rule.test.ts:47:9
windows-unit-tests / windows-unit-tests (24.13.1)
Attempt 1 failed. Reason: Child_process exited with error code 1