Skip to content

service ordering

service ordering #150

Triggered via push April 10, 2026 14:26
Status Failure
Total duration 55s
Artifacts 1

ui-tests.yml

on: push
Matrix: Build and run UI tests
Fit to window
Zoom out
Zoom in

Annotations

15 errors and 2 warnings
Build and run UI tests (24.x)
Process completed with exit code 2.
Build and run UI tests (24.x): frontend/src/pages/stacks/stack-setup.tsx#L71
Object literal may only specify known properties, and 'idField' does not exist in type 'CollectionServiceOptions<ServiceView>'.
Build and run UI tests (24.x): frontend/src/pages/settings/api-tokens-section.tsx#L53
Object literal may only specify known properties, and 'idField' does not exist in type 'CollectionServiceOptions<PublicApiToken>'.
Build and run UI tests (24.x): frontend/src/pages/services/services-list.tsx#L40
Object literal may only specify known properties, and 'idField' does not exist in type 'CollectionServiceOptions<ServiceView>'.
Build and run UI tests (24.x): frontend/src/pages/services/service-detail/history-tab.tsx#L77
Object literal may only specify known properties, and 'idField' does not exist in type 'CollectionServiceOptions<ServiceStateHistory>'.
Build and run UI tests (24.x): frontend/src/components/repository-table.tsx#L37
Object literal may only specify known properties, and 'idField' does not exist in type 'CollectionServiceOptions<GitHubRepository>'.
Build and run UI tests (24.x): frontend/src/components/prerequisite-table.tsx#L43
Object literal may only specify known properties, and 'idField' does not exist in type 'CollectionServiceOptions<Prerequisite>'.
Build and run UI tests (22.x)
The strategy configuration was canceled because "build._24_x" failed
Build and run UI tests (22.x)
The operation was canceled.
Build and run UI tests (22.x): frontend/src/pages/stacks/stack-setup.tsx#L71
Object literal may only specify known properties, and 'idField' does not exist in type 'CollectionServiceOptions<ServiceView>'.
Build and run UI tests (22.x): frontend/src/pages/settings/api-tokens-section.tsx#L53
Object literal may only specify known properties, and 'idField' does not exist in type 'CollectionServiceOptions<PublicApiToken>'.
Build and run UI tests (22.x): frontend/src/pages/services/services-list.tsx#L40
Object literal may only specify known properties, and 'idField' does not exist in type 'CollectionServiceOptions<ServiceView>'.
Build and run UI tests (22.x): frontend/src/pages/services/service-detail/history-tab.tsx#L77
Object literal may only specify known properties, and 'idField' does not exist in type 'CollectionServiceOptions<ServiceStateHistory>'.
Build and run UI tests (22.x): frontend/src/components/repository-table.tsx#L37
Object literal may only specify known properties, and 'idField' does not exist in type 'CollectionServiceOptions<GitHubRepository>'.
Build and run UI tests (22.x): frontend/src/components/prerequisite-table.tsx#L43
Object literal may only specify known properties, and 'idField' does not exist in type 'CollectionServiceOptions<Prerequisite>'.
Build and run UI tests (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@v4, actions/setup-node@v4, actions/upload-artifact@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 and run UI tests (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@v4, actions/setup-node@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/

Artifacts

Produced during runtime
Name Size Digest
ScreenShots
8.15 KB
sha256:008c2bcf434f55b59e2ba5a7720d13fea723441ba22cbe7f062df5e3135f87ad