Fix an error which lead to fallback messages being used needlessly #178
craigfowlerAnnotations
5 errors and 8 warnings
|
Run tests (Chrome, latest-50, Windows, 11)
Process completed with exit code 1.
|
|
Run tests (Chrome, latest-50, Windows, 11)
Process completed with exit code 134.
|
|
Run tests (Chrome, latest-50, Windows, 11)
Process completed with exit code 1.
|
|
Run tests (Firefox, latest-40, Windows, 11)
Process completed with exit code 1.
|
|
Run tests (Firefox, latest-40, Windows, 11)
Process completed with exit code 1.
|
|
Run tests (Chrome, latest-50, Windows, 11)
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-dotnet@v4, actions/upload-artifact@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/
|
|
Run tests (Chrome, latest-50, Windows, 11)
No files were found with the provided path: Tests/**/ScreenplayReport.html. No artifacts will be uploaded.
|
|
Run tests (Chrome, latest, Windows, 11)
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-dotnet@v4, actions/upload-artifact@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/
|
|
Run tests (Edge, latest, Windows, 11)
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-dotnet@v4, actions/upload-artifact@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/
|
|
Run tests (Firefox, latest, Windows, 11)
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-dotnet@v4, actions/upload-artifact@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/
|
|
Run tests (Firefox, latest-40, Windows, 11)
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-dotnet@v4, actions/upload-artifact@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/
|
|
Run tests (Safari, 17.3, OS X, Sonoma)
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-dotnet@v4, actions/upload-artifact@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/
|
|
Run tests (Safari, 26.2, OS X, Tahoe)
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-dotnet@v4, actions/upload-artifact@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/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
Screenplay HTML reports Chrome_latest_Windows_11
Expired
|
70.3 KB |
sha256:268a1a59f0ca49a57e0ffadd8f11c9a7d707e27813973a20ca8fc1b2cc1153d3
|
|
|
Screenplay HTML reports Edge_latest_Windows_11
Expired
|
70.2 KB |
sha256:efa79150cd7d001f50f59921f9c5c621ee6627fee365ec317aa215d9f99ef11d
|
|
|
Screenplay HTML reports Firefox_latest-40_Windows_11
Expired
|
95.6 KB |
sha256:28d508d6dec22a6bafb578b7d10fe34fc3e57e3c1d4c5c515d65a05b184fc259
|
|
|
Screenplay HTML reports Firefox_latest_Windows_11
Expired
|
95.5 KB |
sha256:34740a438e539b36c488a29ec9b7910ee9b9e52f6cfbc007587fe8ba939e31d1
|
|
|
Screenplay HTML reports Safari_17.3_OS X_Sonoma
Expired
|
183 KB |
sha256:e248aec2b609006c3188f866c8df604cc52267383a02a2f42b2ffe36144de503
|
|
|
Screenplay HTML reports Safari_26.2_OS X_Tahoe
Expired
|
204 KB |
sha256:66151f4de9dffdf4df0ebbc76be1580f8de9b85760241bc14fcc0776482e3306
|
|
|
Screenplay JSON reports Chrome_latest-50_Windows_11
Expired
|
7.46 KB |
sha256:837c95b0664af1f5aa2e24d846aec2f569e623bfdbea4dab2aad8d051a73fc42
|
|
|
Screenplay JSON reports Chrome_latest_Windows_11
Expired
|
16.4 KB |
sha256:5dea30f340a867e6c0619a130c575d1c91173af92445239f7d48fdbd58fe721a
|
|
|
Screenplay JSON reports Edge_latest_Windows_11
Expired
|
16.2 KB |
sha256:701a76e75f1179a2d72064d4ef2b90dcad0044662a51057b26d6c446c1f76fcd
|
|
|
Screenplay JSON reports Firefox_latest-40_Windows_11
Expired
|
15.2 KB |
sha256:bb460eceddc85452bcb1f11b3d2bc116ff0cc3359640bb45728d1abfc88007ae
|
|
|
Screenplay JSON reports Firefox_latest_Windows_11
Expired
|
16.1 KB |
sha256:2fd049532eb46fda4db8fc8c4c5090ecbf4b390007424d02f1f5510324c7c036
|
|
|
Screenplay JSON reports Safari_17.3_OS X_Sonoma
Expired
|
16.6 KB |
sha256:ea72c78504a2c8915c923bb213674f41c05c9329a115c9e5992f8fa91d86b041
|
|
|
Screenplay JSON reports Safari_26.2_OS X_Tahoe
Expired
|
16.6 KB |
sha256:a26e7d301154ed8fe0cd47455ee9c90be40d0689d44f8dcc9307033d477d1ca7
|
|