Skip to content
Node.js CI

Node.js CI #1262

Sign in to view logs

Node.js CI

Node.js CI #1262

Triggered via schedule May 5, 2026 10:56
@vitonskyvitonsky
⁠ 0fbb42f
master
Status Failure
Total duration 6m 19s
Artifacts –

node.js.yml

on: schedule
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

14 errors and 3 warnings
src/translators/__tests__/translators.test.ts > Translator YandexTranslator > Translate long text with "translate" method: src/translators/YandexTranslator/index.ts#L62
Error: Invalid SID ❯ YandexTranslator.translateBatch src/translators/YandexTranslator/index.ts:62:10 ❯ src/translators/__tests__/translators.test.ts:297:5
src/translators/__tests__/translators.test.ts > Translator YandexTranslator > Translate many texts with "translateBatch" method: src/translators/YandexTranslator/index.ts#L62
Error: Invalid SID ❯ YandexTranslator.translateBatch src/translators/YandexTranslator/index.ts:62:10 ❯ src/translators/__tests__/translators.test.ts:273:24
src/translators/__tests__/translators.test.ts > Translator YandexTranslator > Translate 2 texts with "translateBatch" method: src/translators/YandexTranslator/index.ts#L62
Error: Invalid SID ❯ YandexTranslator.translateBatch src/translators/YandexTranslator/index.ts:62:10 ❯ src/translators/__tests__/translators.test.ts:244:4
src/translators/__tests__/translators.test.ts > Translator YandexTranslator > Translate 1 text with "translateBatch" method: src/translators/YandexTranslator/index.ts#L62
Error: Invalid SID ❯ YandexTranslator.translateBatch src/translators/YandexTranslator/index.ts:62:10 ❯ src/translators/__tests__/translators.test.ts:229:4
src/translators/__tests__/translators.test.ts > Translator YandexTranslator > Translate results are correct > Batch translator call with multiple texts, returns texts that does not contains original text: src/translators/YandexTranslator/index.ts#L62
Error: Invalid SID ❯ YandexTranslator.translateBatch src/translators/YandexTranslator/index.ts:62:10 ❯ src/translators/__tests__/translators.test.ts:214:5
src/translators/__tests__/translators.test.ts > Translator YandexTranslator > Translate results are correct > Batch translator call with single text, returns text that does not contains original text: src/translators/YandexTranslator/index.ts#L62
Error: Invalid SID ❯ YandexTranslator.translateBatch src/translators/YandexTranslator/index.ts:62:10 ❯ src/translators/__tests__/translators.test.ts:200:5
src/translators/__tests__/translators.test.ts > Translator YandexTranslator > Translate one text with method "translate": src/translators/YandexTranslator/index.ts#L62
Error: Invalid SID ❯ YandexTranslator.translateBatch src/translators/YandexTranslator/index.ts:62:10 ❯ src/translators/__tests__/translators.test.ts:188:4
src/translators/__tests__/translators.test.ts > Translator YandexTranslator > Method "translate" supports chinese language: src/translators/YandexTranslator/index.ts#L62
Error: Invalid SID ❯ YandexTranslator.translateBatch src/translators/YandexTranslator/index.ts:62:10 ❯ src/translators/__tests__/translators.test.ts:176:5
src/translators/__tests__/translators.benchmark.test.ts > Top translators list with score: src/translators/__tests__/translators.benchmark.test.ts#L54
AssertionError: promise rejected "Error: Invalid SID" instead of resolving ❯ test.timeout src/translators/__tests__/translators.benchmark.test.ts:54:3 Caused by: Caused by: Error: Invalid SID ❯ YandexTranslator.translateBatch src/translators/YandexTranslator/index.ts:62:10 ❯ getTranslatorsScore src/translators/__tests__/benchmark.ts:56:23 ❯ test.timeout src/translators/__tests__/translators.benchmark.test.ts:43:3
Unhandled error: src/translators/YandexTranslator/index.ts#L62
Error: Invalid SID ❯ YandexTranslator.translateBatch src/translators/YandexTranslator/index.ts:62:10 This error originated in "src/translators/__tests__/translators.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "Translate 2 texts with "translateBatch" method". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.
build (24.x)
The strategy configuration was canceled because "build._20_x" failed
build (24.x)
The operation was canceled.
build (22.x)
The strategy configuration was canceled because "build._20_x" failed
build (22.x)
The operation was canceled.
build (20.x)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-node@v3. 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/
build (24.x)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-node@v3. 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/
build (22.x)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-node@v3. 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/