build(deps): bump vite, @vitest/coverage-v8 and vitest #19
coverage.yml
on: pull_request
coverage — ubuntu
2m 29s
Annotations
10 errors and 2 warnings
|
test/unit/Operations.annotate.test.js > Operations annotate-mode (T-0009) > constructor > sets annotateMode=false by default:
src/Operations.js#L51
TypeError: () => ({
init: vi.fn().mockResolvedValue(undefined),
generateKey: __vite_ssr_impo...<omitted>...}) is not a constructor
❯ new Operations src/Operations.js:51:29
❯ test/unit/Operations.annotate.test.js:112:25
|
|
test/unit/ContextPool.test.js > ContextPool — maxClients=1 single-client mode > behaves serially: second checkout waits for first to complete:
src/server/ContextPool.js#L166
TypeError: () => ({
extracts: [],
tokenUsage: { prompt: 0, completion: 0, total: 0 },
executionIndex: 0,
p...<omitted>...}) is not a constructor
❯ ContextPool._allocate src/server/ContextPool.js:166:19
❯ test/unit/ContextPool.test.js:231:16
|
|
test/unit/ContextPool.test.js > ContextPool — drain > drain rejects all queued waiters:
src/server/ContextPool.js#L166
TypeError: () => ({
extracts: [],
tokenUsage: { prompt: 0, completion: 0, total: 0 },
executionIndex: 0,
p...<omitted>...}) is not a constructor
❯ ContextPool._allocate src/server/ContextPool.js:166:19
❯ test/unit/ContextPool.test.js:207:16
|
|
test/unit/ContextPool.test.js > ContextPool — queueing > queue timeout rejects waiter when no slot freed in time:
src/server/ContextPool.js#L166
TypeError: () => ({
extracts: [],
tokenUsage: { prompt: 0, completion: 0, total: 0 },
executionIndex: 0,
p...<omitted>...}) is not a constructor
❯ ContextPool._allocate src/server/ContextPool.js:166:19
❯ test/unit/ContextPool.test.js:193:16
|
|
test/unit/ContextPool.test.js > ContextPool — queueing > queue depth is reported correctly:
src/server/ContextPool.js#L166
TypeError: () => ({
extracts: [],
tokenUsage: { prompt: 0, completion: 0, total: 0 },
executionIndex: 0,
p...<omitted>...}) is not a constructor
❯ ContextPool._allocate src/server/ContextPool.js:166:19
❯ test/unit/ContextPool.test.js:172:16
|
|
test/unit/ContextPool.test.js > ContextPool — queueing > (N+1)th checkout queues until a slot is freed:
src/server/ContextPool.js#L166
TypeError: () => ({
extracts: [],
tokenUsage: { prompt: 0, completion: 0, total: 0 },
executionIndex: 0,
p...<omitted>...}) is not a constructor
❯ ContextPool._allocate src/server/ContextPool.js:166:19
❯ test/unit/ContextPool.test.js:146:16
|
|
test/unit/ContextPool.test.js > ContextPool — isolation > each slot has distinct context + page + ops instances:
src/server/ContextPool.js#L166
TypeError: () => ({
extracts: [],
tokenUsage: { prompt: 0, completion: 0, total: 0 },
executionIndex: 0,
p...<omitted>...}) is not a constructor
❯ ContextPool._allocate src/server/ContextPool.js:166:19
❯ test/unit/ContextPool.test.js:129:16
|
|
test/unit/ContextPool.test.js > ContextPool — basic lifecycle > active count tracks in-flight slots:
src/server/ContextPool.js#L166
TypeError: () => ({
extracts: [],
tokenUsage: { prompt: 0, completion: 0, total: 0 },
executionIndex: 0,
p...<omitted>...}) is not a constructor
❯ ContextPool._allocate src/server/ContextPool.js:166:19
❯ test/unit/ContextPool.test.js:113:16
|
|
test/unit/ContextPool.test.js > ContextPool — basic lifecycle > checkin closes the context:
src/server/ContextPool.js#L166
TypeError: () => ({
extracts: [],
tokenUsage: { prompt: 0, completion: 0, total: 0 },
executionIndex: 0,
p...<omitted>...}) is not a constructor
❯ ContextPool._allocate src/server/ContextPool.js:166:19
❯ test/unit/ContextPool.test.js:103:18
|
|
test/unit/ContextPool.test.js > ContextPool — basic lifecycle > checkout returns a slot with context, page, ops:
src/server/ContextPool.js#L166
TypeError: () => ({
extracts: [],
tokenUsage: { prompt: 0, completion: 0, total: 0 },
executionIndex: 0,
p...<omitted>...}) is not a constructor
❯ ContextPool._allocate src/server/ContextPool.js:166:19
❯ test/unit/ContextPool.test.js:90:18
|
|
coverage — ubuntu
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5. 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/
|
|
coverage — ubuntu
No files were found with the provided path: coverage/. No artifacts will be uploaded.
|