Skip to content

fix: silently skip edited comment events instead of logging errors #2428

fix: silently skip edited comment events instead of logging errors

fix: silently skip edited comment events instead of logging errors #2428

Triggered via pull request April 8, 2026 09:47
@majiayu000majiayu000
opened #2657
Status Failure
Total duration 18s
Artifacts 9

e2e.yaml

on: pull_request_target
Matrix: e2e tests
Notify Slack on Failures
0s
Notify Slack on Failures
Fit to window
Zoom out
Zoom in

Annotations

18 errors and 9 warnings
e2e tests (github_ghe_1)
Process completed with exit code 1.
e2e tests (github_ghe_1)
❌ Permission denied: @majiayu000 is not a trusted bot, org/team member, or repo collaborator with 'write' access. A maintainer can approve by adding the 'ok-to-test' label.
e2e tests (github_ghe_3)
Process completed with exit code 1.
e2e tests (github_ghe_3)
❌ Permission denied: @majiayu000 is not a trusted bot, org/team member, or repo collaborator with 'write' access. A maintainer can approve by adding the 'ok-to-test' label.
e2e tests (gitea_1)
Process completed with exit code 1.
e2e tests (gitea_1)
❌ Permission denied: @majiayu000 is not a trusted bot, org/team member, or repo collaborator with 'write' access. A maintainer can approve by adding the 'ok-to-test' label.
e2e tests (gitlab_bitbucket)
Process completed with exit code 1.
e2e tests (gitlab_bitbucket)
❌ Permission denied: @majiayu000 is not a trusted bot, org/team member, or repo collaborator with 'write' access. A maintainer can approve by adding the 'ok-to-test' label.
e2e tests (gitea_2)
Process completed with exit code 1.
e2e tests (gitea_2)
❌ Permission denied: @majiayu000 is not a trusted bot, org/team member, or repo collaborator with 'write' access. A maintainer can approve by adding the 'ok-to-test' label.
e2e tests (github_public)
Process completed with exit code 1.
e2e tests (github_public)
❌ Permission denied: @majiayu000 is not a trusted bot, org/team member, or repo collaborator with 'write' access. A maintainer can approve by adding the 'ok-to-test' label.
e2e tests (concurrency)
Process completed with exit code 1.
e2e tests (concurrency)
❌ Permission denied: @majiayu000 is not a trusted bot, org/team member, or repo collaborator with 'write' access. A maintainer can approve by adding the 'ok-to-test' label.
e2e tests (gitea_3)
Process completed with exit code 1.
e2e tests (gitea_3)
❌ Permission denied: @majiayu000 is not a trusted bot, org/team member, or repo collaborator with 'write' access. A maintainer can approve by adding the 'ok-to-test' label.
e2e tests (github_ghe_2)
Process completed with exit code 1.
e2e tests (github_ghe_2)
❌ Permission denied: @majiayu000 is not a trusted bot, org/team member, or repo collaborator with 'write' access. A maintainer can approve by adding the 'ok-to-test' label.
e2e tests (github_ghe_1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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 tests (github_ghe_3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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 tests (gitea_1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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 tests (gitlab_bitbucket)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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 tests (gitea_2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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 tests (github_public)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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 tests (concurrency)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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 tests (gitea_3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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 tests (github_ghe_2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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/

Artifacts

Produced during runtime
Name Size Digest
logs-e2e-tests-concurrency
140 Bytes
sha256:947565ed764e49759a276dd517534b9e0d8aa1576bc4f8a743605931f4dc274a
logs-e2e-tests-gitea_1
140 Bytes
sha256:2aa550cc2593af170fba722ec4226fab83481a49674d31469a278f921ccfec46
logs-e2e-tests-gitea_2
140 Bytes
sha256:2aa550cc2593af170fba722ec4226fab83481a49674d31469a278f921ccfec46
logs-e2e-tests-gitea_3
140 Bytes
sha256:2aa550cc2593af170fba722ec4226fab83481a49674d31469a278f921ccfec46
logs-e2e-tests-github_ghe_1
140 Bytes
sha256:bbe3277fbfba16459b0abbce2c48de62b1687ea78898b4ea7f294432e03f847a
logs-e2e-tests-github_ghe_2
140 Bytes
sha256:2aa550cc2593af170fba722ec4226fab83481a49674d31469a278f921ccfec46
logs-e2e-tests-github_ghe_3
140 Bytes
sha256:bbe3277fbfba16459b0abbce2c48de62b1687ea78898b4ea7f294432e03f847a
logs-e2e-tests-github_public
140 Bytes
sha256:2aa550cc2593af170fba722ec4226fab83481a49674d31469a278f921ccfec46
logs-e2e-tests-gitlab_bitbucket
140 Bytes
sha256:bbe3277fbfba16459b0abbce2c48de62b1687ea78898b4ea7f294432e03f847a