Test: Full Suite #768
test-full-suite.yml
on: workflow_dispatch
validate-commit
16s
Matrix: e2e / e2e-windows-run
e2e
/
e2e-debian
e2e
/
e2e-debian
e2e
/
e2e-rhel
e2e
/
e2e-rhel
e2e
/
e2e-sles
e2e
/
e2e-sles
e2e
/
e2e-suse
e2e
/
e2e-suse
test
/
integration
test
/
unit
slack-notify
3s
Annotations
38 errors and 20 warnings
|
e2e / chromium-2
Process completed with exit code 2.
|
|
e2e / chromium-3
Process completed with exit code 2.
|
|
e2e / chromium-1
Process completed with exit code 2.
|
|
e2e / electron-4
Process completed with exit code 2.
|
|
e2e / chromium-4
Process completed with exit code 2.
|
|
e2e / electron-1
Process completed with exit code 2.
|
|
e2e / electron-2
Process completed with exit code 2.
|
|
e2e / chromium
Process completed with exit code 1.
|
|
e2e / chromium
Process completed with exit code 1.
|
|
e2e / electron-3
Process completed with exit code 2.
|
|
e2e / electron
Process completed with exit code 1.
|
|
e2e / electron
Process completed with exit code 1.
|
|
e2e / windows-1
Process completed with exit code 1.
|
|
e2e / windows-1
Property 'page' is private and only accessible within class 'PlaywrightDriver'.
|
|
e2e / windows-1
Property 'page' is private and only accessible within class 'PlaywrightDriver'.
|
|
e2e / windows-1
Property 'page' is private and only accessible within class 'PlaywrightDriver'.
|
|
e2e / windows-1
Property 'page' is private and only accessible within class 'PlaywrightDriver'.
|
|
e2e / windows-1
Property 'page' is private and only accessible within class 'PlaywrightDriver'.
|
|
e2e / windows-4
Process completed with exit code 1.
|
|
e2e / windows-4
Property 'page' is private and only accessible within class 'PlaywrightDriver'.
|
|
e2e / windows-4
Property 'page' is private and only accessible within class 'PlaywrightDriver'.
|
|
e2e / windows-4
Property 'page' is private and only accessible within class 'PlaywrightDriver'.
|
|
e2e / windows-4
Property 'page' is private and only accessible within class 'PlaywrightDriver'.
|
|
e2e / windows-4
Property 'page' is private and only accessible within class 'PlaywrightDriver'.
|
|
e2e / windows-3
Process completed with exit code 1.
|
|
e2e / windows-3
Property 'page' is private and only accessible within class 'PlaywrightDriver'.
|
|
e2e / windows-3
Property 'page' is private and only accessible within class 'PlaywrightDriver'.
|
|
e2e / windows-3
Property 'page' is private and only accessible within class 'PlaywrightDriver'.
|
|
e2e / windows-3
Property 'page' is private and only accessible within class 'PlaywrightDriver'.
|
|
e2e / windows-3
Property 'page' is private and only accessible within class 'PlaywrightDriver'.
|
|
e2e / windows-2
Process completed with exit code 1.
|
|
e2e / windows-2
Property 'page' is private and only accessible within class 'PlaywrightDriver'.
|
|
e2e / windows-2
Property 'page' is private and only accessible within class 'PlaywrightDriver'.
|
|
e2e / windows-2
Property 'page' is private and only accessible within class 'PlaywrightDriver'.
|
|
e2e / windows-2
Property 'page' is private and only accessible within class 'PlaywrightDriver'.
|
|
e2e / windows-2
Property 'page' is private and only accessible within class 'PlaywrightDriver'.
|
|
e2e / windows
Process completed with exit code 1.
|
|
e2e / windows
Process completed with exit code 1.
|
|
setup / build-ubuntu
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: nick-fields/retry@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/
|
|
e2e / chromium-2
No files were found with the provided path: blob-report. No artifacts will be uploaded.
|
|
e2e / chromium-3
No files were found with the provided path: blob-report. No artifacts will be uploaded.
|
|
e2e / chromium-1
No files were found with the provided path: blob-report. No artifacts will be uploaded.
|
|
e2e / electron-4
No files were found with the provided path: blob-report. No artifacts will be uploaded.
|
|
e2e / chromium-4
No files were found with the provided path: blob-report. No artifacts will be uploaded.
|
|
e2e / electron-1
No files were found with the provided path: blob-report. No artifacts will be uploaded.
|
|
e2e / electron-2
No files were found with the provided path: blob-report. No artifacts will be uploaded.
|
|
e2e / chromium
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/configure-aws-credentials@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 / chromium
Missing blob reports for shards: 1 2 3 4
|
|
e2e / electron-3
No files were found with the provided path: blob-report. No artifacts will be uploaded.
|
|
e2e / electron
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/configure-aws-credentials@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 / electron
Missing blob reports for shards: 1 2 3 4
|
|
e2e / windows-1
No files were found with the provided path: blob-report. No artifacts will be uploaded.
|
|
e2e / windows-4
No files were found with the provided path: blob-report. No artifacts will be uploaded.
|
|
e2e / windows-3
No files were found with the provided path: blob-report. No artifacts will be uploaded.
|
|
e2e / windows-2
No files were found with the provided path: blob-report. No artifacts will be uploaded.
|
|
e2e / windows
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/configure-aws-credentials@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 / windows
Missing blob reports for shards: 1 2 3 4
|
|
slack-notify
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: midleman/slack-workflow-status@v3.1.3. 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 | |
|---|---|---|---|
|
positron-build
Expired
|
2.22 GB |
sha256:a14a4e43cc2cd94ac4fc4fb83d7c249c157c5f0c8bd8e00d47c016cbab087f44
|
|