T2564: Investigate and fix taskcore claim endpoint #2
krandderci.yml
on: pull_request
TypeScript type check
10s
Core unit tests
5m 18s
Middle integration tests
8s
Annotations
9 errors and 3 warnings
|
TypeScript type check
Process completed with exit code 2.
|
|
TypeScript type check:
middle/test/finalize.test.ts#L42
Property 'path' does not exist on type 'ArtifactEvidence'.
|
|
TypeScript type check:
middle/test/finalize.test.ts#L42
This comparison appears to be unintentional because the types 'ArtifactKind' and '"file"' have no overlap.
|
|
TypeScript type check:
middle/http.ts#L2017
Object literal may only specify known properties, and 'source' does not exist in type 'TaskFailed'.
|
|
TypeScript type check:
middle/http.ts#L1903
Object literal may only specify known properties, and 'source' does not exist in type 'TaskCompleted'.
|
|
TypeScript type check:
middle/http.ts#L1821
Object literal may only specify known properties, and 'source' does not exist in type 'TaskCompleted'.
|
|
TypeScript type check:
middle/finalize.ts#L224
Type '"file"' is not assignable to type 'ArtifactKind'.
|
|
Core unit tests
The job has exceeded the maximum execution time of 5m0s
|
|
Core unit tests
The operation was canceled.
|
|
Middle integration tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
TypeScript type check
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Core unit tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|