Skip to content
Coverage Check

Feature/create commitment upper bounds #212

Sign in to view logs

Feature/create commitment upper bounds

Feature/create commitment upper bounds #212

Triggered via pull request May 28, 2026 14:20
@1nonlypiece1nonlypiece
synchronize #543
egwujiohaifesinachiperpetual-max:feature/create-commitment-upper-bounds
Status Failure
Total duration 1m 41s
Artifacts –

coverage.yml

on: pull_request
Vitest Coverage
1m 34s
Vitest Coverage
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 2 warnings
tests/api/commitmentHistory.test.ts > GET /api/commitments/[id]/history > paginates results with page and pageSize params: tests/api/commitmentHistory.test.ts#L243
AssertionError: expected 404 to be 200 // Object.is equality - Expected + Received - 200 + 404 ❯ tests/api/commitmentHistory.test.ts:243:27
tests/api/commitmentHistory.test.ts > GET /api/commitments/[id]/history > orders events oldest-first regardless of insertion order: tests/api/commitmentHistory.test.ts#L230
TypeError: Cannot destructure property 'events' of 'result.data.data' as it is undefined. ❯ tests/api/commitmentHistory.test.ts:230:13
tests/api/commitmentHistory.test.ts > GET /api/commitments/[id]/history > does not include terminal event for ACTIVE commitment: tests/api/commitmentHistory.test.ts#L216
TypeError: Cannot destructure property 'events' of 'result.data.data' as it is undefined. ❯ tests/api/commitmentHistory.test.ts:216:13
tests/api/commitmentHistory.test.ts > GET /api/commitments/[id]/history > includes settlement event when commitment status is SETTLED: tests/api/commitmentHistory.test.ts#L206
TypeError: Cannot destructure property 'events' of 'result.data.data' as it is undefined. ❯ tests/api/commitmentHistory.test.ts:206:13
tests/api/commitmentHistory.test.ts > GET /api/commitments/[id]/history > includes early_exit event when commitment status is EARLY_EXIT: tests/api/commitmentHistory.test.ts#L196
TypeError: Cannot destructure property 'events' of 'result.data.data' as it is undefined. ❯ tests/api/commitmentHistory.test.ts:196:13
tests/api/commitmentHistory.test.ts > GET /api/commitments/[id]/history > attestation event has correct shape: tests/api/commitmentHistory.test.ts#L174
TypeError: Cannot read properties of undefined (reading 'events') ❯ tests/api/commitmentHistory.test.ts:174:40
tests/api/commitmentHistory.test.ts > GET /api/commitments/[id]/history > created event has correct shape: tests/api/commitmentHistory.test.ts#L158
TypeError: Cannot read properties of undefined (reading 'events') ❯ tests/api/commitmentHistory.test.ts:158:36
tests/api/commitmentHistory.test.ts > GET /api/commitments/[id]/history > excludes attestations belonging to other commitments: tests/api/commitmentHistory.test.ts#L146
TypeError: Cannot destructure property 'events' of 'result.data.data' as it is undefined. ❯ tests/api/commitmentHistory.test.ts:146:13
tests/api/commitmentHistory.test.ts > GET /api/commitments/[id]/history > returns created + attestation events in chronological order: tests/api/commitmentHistory.test.ts#L126
AssertionError: expected 404 to be 200 // Object.is equality - Expected + Received - 200 + 404 ❯ tests/api/commitmentHistory.test.ts:126:27
tests/api/commitmentHistory.test.ts > GET /api/commitments/[id]/history > returns only a created event when there are no attestations: tests/api/commitmentHistory.test.ts#L114
AssertionError: expected 404 to be 200 // Object.is equality - Expected + Received - 200 + 404 ❯ tests/api/commitmentHistory.test.ts:114:27
Vitest Coverage
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, actions/upload-artifact@v4, pnpm/action-setup@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Vitest Coverage
No files were found with the provided path: coverage/. No artifacts will be uploaded.