Skip to content

FE-588: Add basic Scenario support #29268

FE-588: Add basic Scenario support

FE-588: Add basic Scenario support #29268

Triggered via pull request April 7, 2026 08:33
Status Success
Total duration 18m 22s
Artifacts 3

test.yml

on: pull_request
Matrix: Publish
Matrix: Unit
Matrix: Build
Matrix: Integration
Tests passed
12s
Tests passed
Fit to window
Zoom out
Zoom in

Annotations

1 error, 5 warnings, and 5 notices
[chromium] › tests/entities-page.spec.ts:10:1 › user can visit a page listing entities of a type: tests/hash-playwright/tests/entities-page.spec.ts#L32
1) [chromium] › tests/entities-page.spec.ts:10:1 › user can visit a page listing entities of a type Error: expect(locator).toBeVisible() failed Locator: locator('text=Document').first() Expected: visible Received: hidden Timeout: 5000ms Call log: - Expect "toBeVisible" with timeout 5000ms - waiting for locator('text=Document').first() 3 × locator resolved to <span data-sentry-element="Typography" data-sentry-source-file="entity-or-type-sidebar-item.tsx" class="MuiTypography-root MuiTypography-smallTextLabels css-mpg5zb">…</span> - unexpected value "hidden" 30 | // Wait for 'Document' to be visible before clicking (sidebar expand animation) 31 | const documentItem = page.locator("text=Document").first(); > 32 | await expect(documentItem).toBeVisible(); | ^ 33 | await documentItem.click(); 34 | 35 | // Check if we are on the 'Document' entities page at /home/runner/work/hash/hash/tests/hash-playwright/tests/entities-page.spec.ts:32:30
Optimize CI
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: withgraphite/graphite-ci-action@ee395f3a78254c006d11339669c6cabddf196f72. 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/
setup
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@0057852bfaa89a56745cba8c7296529d2fc39830, jdx/mise-action@146a28175021df8ca24f8ee1828cc2a60f980bd5. 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/
Unit (@hashintel/petrinaut)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@0057852bfaa89a56745cba8c7296529d2fc39830, actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea, hashicorp/vault-action@4c06c5ccf5c0761b6029f56cfb1dcf5565918a3b, jdx/mise-action@146a28175021df8ca24f8ee1828cc2a60f980bd5, mozilla-actions/***-action@7d986dd989559c6ecdb630a3fd2557667be217ad, nick-fields/retry@ce71cc2ab81d554ebbe88c79ab5975992d79ba08. 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 (@apps/hash-frontend)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@263435318d21b8e681c14492fe198d362a7d2c83, docker/login-action@5e57cd118135c172c3672efd75eb46360885c0ef, docker/setup-buildx-action@e468171a9de216ec08956ac3ada2f0791b6bd435. 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/
Integration (@tests/hash-playwright)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@0057852bfaa89a56745cba8c7296529d2fc39830, actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02, hashicorp/vault-action@4c06c5ccf5c0761b6029f56cfb1dcf5565918a3b, jdx/mise-action@146a28175021df8ca24f8ee1828cc2a60f980bd5, mozilla-actions/***-action@7d986dd989559c6ecdb630a3fd2557667be217ad, nick-fields/retry@ce71cc2ab81d554ebbe88c79ab5975992d79ba08. 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/
sccache stats
0% - 0 hits, 0 misses, 0 errors
Unit (@hashintel/petrinaut)
*** server started successfully on port 4226
sccache stats
100% - 1335 hits, 2 misses, 0 errors
🎭 Playwright Run Summary
1 flaky [chromium] › tests/entities-page.spec.ts:10:1 › user can visit a page listing entities of a type 10 skipped 19 passed (3.1m)
Integration (@tests/hash-playwright)
*** server started successfully on port 4226

Artifacts

Produced during runtime
Name Size Digest
hashintel~hash~I9QWCB.dockerbuild
125 KB
sha256:684be16a8349e88644711229ac8327537f86a8c1b36cff11851192b9ff72374c
tests.hash-playwright_logs
59.5 KB
sha256:0db470843f8ff9a80215240d8eb6c70ac83339735424b160adc1ad57b0a90fce
tests.hash-playwright_report
4.26 MB
sha256:c00cc876fdeb6fc4152395019cd73979b3ec0ba1049a34363995f407cc64543f