Skip to content

feat: coar notify US4, announce ingest #4337

feat: coar notify US4, announce ingest

feat: coar notify US4, announce ingest #4337

Triggered via pull request April 2, 2026 20:12
@3mcd3mcd
synchronize #1429
em/coar-us4
Status Failure
Total duration 11m 0s
Artifacts 4

on_pr.yml

on: pull_request
path-filter
12s
path-filter
skip_build_sha
8s
skip_build_sha
Matrix: ci / ci
close-preview  /  preview
close-preview / preview
close-docs-preview
0s
close-docs-preview
deploy-docs-preview  /  build-docs
deploy-docs-preview / build-docs
build-all  /  Emit container tag sha
5s
build-all / Emit container tag sha
build-all  /  ...  /  Build
3m 44s
build-all / build-base / Build
build-all  /  ...  /  Build
4m 36s
build-all / build-core / Build
build-all  /  ...  /  Build
1m 51s
build-all / build-jobs / Build
build-all  /  ...  /  Build
2m 19s
build-all / build-site-builder / Build
Matrix: e2e / Integration tests
deploy-preview  /  preview
21s
deploy-preview / preview
status-check
0s
status-check
Fit to window
Zoom out
Zoom in

Annotations

7 errors, 12 warnings, and 2 notices
ci / ci (lint:ci)
Process completed with exit code 1.
ci / ci (type-check)
The strategy configuration was canceled because "ci.ci.lint_ci" failed
ci / ci (type-check)
The operation was canceled.
ci / ci (test-run)
The strategy configuration was canceled because "ci.ci.lint_ci" failed
ci / ci (test-run)
The operation was canceled.
[chromium] › playwright/coar-notify.spec.ts:816:2 › User Story 2: Review Group Receives Review Request › Review group receives Offer: core/playwright/fixtures/stages-manage-page.ts#L72
1) [chromium] › playwright/coar-notify.spec.ts:816:2 › User Story 2: Review Group Receives Review Request › Review group receives Offer, processes review, and sends Announce Error: locator.click: Test timeout of 30000ms exceeded. Call log: - waiting for getByRole('dialog').getByRole('tab', { name: 'Pubs' }) at fixtures/stages-manage-page.ts:72 70 | await this.openStagePanel(stageName) 71 | const stagePanel = this.page.getByRole("dialog") > 72 | await stagePanel.getByRole("tab", { name: tab }).click() | ^ 73 | } 74 | 75 | /** at StagesManagePage.openStagePanelTab (/home/runner/work/pubplatform/pubplatform/core/playwright/fixtures/stages-manage-page.ts:72:52) at /home/runner/work/pubplatform/pubplatform/core/playwright/coar-notify.spec.ts:855:3
[chromium] › playwright/coar-notify.spec.ts:816:2 › User Story 2: Review Group Receives Review Request › Review group receives Offer: core/playwright/coar-notify.spec.ts#L0
1) [chromium] › playwright/coar-notify.spec.ts:816:2 › User Story 2: Review Group Receives Review Request › Review group receives Offer, processes review, and sends Announce Test timeout of 30000ms exceeded.
skip_build_sha
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 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/
path-filter
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, dorny/paths-filter@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-all / Emit container tag sha
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 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/
ci / ci (lint:ci)
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, 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/
ci / ci (type-check)
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, 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/
ci / ci (test-run)
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, 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/
build-all / build-jobs / Build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, aws-actions/aws-secretsmanager-get-secrets@v2, aws-actions/configure-aws-credentials@v4, docker/build-push-action@v6, docker/login-action@v3, docker/setup-buildx-action@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-all / build-site-builder / Build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, aws-actions/aws-secretsmanager-get-secrets@v2, aws-actions/configure-aws-credentials@v4, docker/build-push-action@v6, docker/login-action@v3, docker/setup-buildx-action@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-all / build-base / Build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, aws-actions/aws-secretsmanager-get-secrets@v2, aws-actions/configure-aws-credentials@v4, docker/build-push-action@v6, docker/login-action@v3, docker/setup-buildx-action@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-all / build-core / Build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, aws-actions/aws-secretsmanager-get-secrets@v2, aws-actions/configure-aws-credentials@v4, docker/build-push-action@v6, docker/login-action@v3, docker/setup-buildx-action@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/
deploy-preview / preview
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 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/
e2e / Integration tests (core)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/checkout@v4, actions/setup-node@v4, aws-actions/configure-aws-credentials@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/
🎭 Playwright Run Summary
1 flaky [chromium] › playwright/coar-notify.spec.ts:816:2 › User Story 2: Review Group Receives Review Request › Review group receives Offer, processes review, and sends Announce 19 skipped 114 passed (3.4m)
🎭 Playwright Run Summary
1 passed (8.1s)

Artifacts

Produced during runtime
Name Size Digest
knowledgefutures~pubplatform~L5AJEZ.dockerbuild
65.4 KB
sha256:81d450e07713bf4c81167d863d610dc68674b31afe52182c830722783bc325c4
knowledgefutures~pubplatform~R58D4V.dockerbuild
62.7 KB
sha256:b36f28a99eeb051a185304e9fc3c90040fa597bf0ec87c7624d949d4ab8ef735
knowledgefutures~pubplatform~V795AL.dockerbuild
61.2 KB
sha256:8cf021124d2f7ecf87156083db1308bcf58c3589f15f37ed8f326dcc742fae10
knowledgefutures~pubplatform~X5AV1L.dockerbuild
67.5 KB
sha256:1079bdd3d941aea8758d2217aa6ea3517650567371b43a47fc66161224ac1f65