Skip to content

feat: DH-21476: Middleware plugin infrastructure for widget chaining #5296

feat: DH-21476: Middleware plugin infrastructure for widget chaining

feat: DH-21476: Middleware plugin infrastructure for widget chaining #5296

Triggered via pull request May 4, 2026 13:50
Status Success
Total duration 22m 41s
Artifacts 6

e2e.yml

on: pull_request
Matrix: e2e-tests
merge-reports
18s
merge-reports
e2e-results
3s
e2e-results
Fit to window
Zoom out
Zoom in

Annotations

2 errors, 6 warnings, and 1 notice
[webkit] › ../../../../../work/tests/golden-layout.spec.ts:145:7 › tests golden-layout operations › golden-layout can drag tab to left edge: ../../../../../work/tests/golden-layout.spec.ts#L40
1) [webkit] › ../../../../../work/tests/golden-layout.spec.ts:145:7 › tests golden-layout operations › golden-layout can drag tab to left edge TimeoutError: locator.click: Timeout 15000ms exceeded. Call log: - waiting for getByTestId('app-main-panels-button') - locator resolved to <button type="button" data-testid="app-main-panels-button" class="btn btn-link btn-panels-menu btn-show-panels">…</button> - attempting click action 2 × waiting for element to be visible, enabled and stable - element is visible, enabled and stable - scrolling into view if needed - done scrolling - <html lang="en">…</html> intercepts pointer events - retrying click action - waiting 20ms 2 × waiting for element to be visible, enabled and stable - element is visible, enabled and stable - scrolling into view if needed - done scrolling - <html lang="en">…</html> intercepts pointer events - retrying click action - waiting 100ms 27 × waiting for element to be visible, enabled and stable - element is visible, enabled and stable - scrolling into view if needed - done scrolling - <html lang="en">…</html> intercepts pointer events - retrying click action - waiting 500ms 38 | */ 39 | async function resetLayout(confirm: boolean) { > 40 | await page.getByTestId('app-main-panels-button').click(); | ^ 41 | await page.getByLabel('Reset Layout').click(); 42 | 43 | if (confirm) { at resetLayout (/work/tests/golden-layout.spec.ts:40:56) at /work/tests/golden-layout.spec.ts:59:11
[webkit] › ../../../../../work/tests/golden-layout.spec.ts:145:7 › tests golden-layout operations › golden-layout can drag tab to left edge: ../../../../../work/tests/golden-layout.spec.ts#L167
1) [webkit] › ../../../../../work/tests/golden-layout.spec.ts:145:7 › tests golden-layout operations › golden-layout can drag tab to left edge Error: expect(locator).toHaveScreenshot(expected) failed Locator: locator('.lm_dropTargetIndicator') 3 pixels (ratio 0.01 of all image pixels) are different. Call log: - Expect "toHaveScreenshot" with timeout 15000ms - verifying given screenshot expectation - waiting for locator('.lm_dropTargetIndicator') - locator resolved to <div class="lm_dropTargetIndicator">…</div> - taking element screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - attempting scroll into view action - waiting for element to be stable - 3 pixels (ratio 0.01 of all image pixels) are different. - waiting 100ms before taking screenshot - waiting for locator('.lm_dropTargetIndicator') - locator resolved to <div class="lm_dropTargetIndicator">…</div> - taking element screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - attempting scroll into view action - waiting for element to be stable - captured a stable screenshot - 3 pixels (ratio 0.01 of all image pixels) are different. 165 | 166 | // check the drop indicator > 167 | await expect(dropTargetIndicator).toHaveScreenshot(); | ^ 168 | 169 | // check the drag proxy 170 | await expect(page.locator('.lm_dragProxy')).toHaveScreenshot(); at /work/tests/golden-layout.spec.ts:167:39
build
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/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/
e2e-tests (webkit-1-2)
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/download-artifact@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/
e2e-tests (webkit-2-2)
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/download-artifact@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/
e2e-tests (firefox-1-1)
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/download-artifact@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/
e2e-tests (chromium-1-1)
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/download-artifact@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/
merge-reports
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@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/
🎭 Playwright Run Summary
1 flaky [webkit] › ../../../../../work/tests/golden-layout.spec.ts:145:7 › tests golden-layout operations › golden-layout can drag tab to left edge 356 passed (9.9m)

Artifacts

Produced during runtime
Name Size Digest
image-cache Expired
1.54 GB
sha256:e7c935b0abd55033350b5ad0dee2989f84d3f1aa3253a668433beaf91cb9da2a
playwright-report
7.15 MB
sha256:5f903749c6f2c211531a9cdb96e098b4bda4206b52d425f77ad8563eb2445d4d
playwright-report-blob-chromium-1-1 Expired
176 KB
sha256:88f943806ec443dfc6bfa2ba91b342c481ecda027223e6ca9696e070f590fb52
playwright-report-blob-firefox-1-1 Expired
177 KB
sha256:647b8cc368f37b0a84a4bc07600b6be7c4469b9af661a87f9eb832049dee6eb9
playwright-report-blob-webkit-1-2 Expired
6.46 MB
sha256:77b674825b60c93c508a041a97d196afff4cff3730372a83cd0f59bf37ace519
playwright-report-blob-webkit-2-2 Expired
119 KB
sha256:2ca5d956bfb2f8521ebc296bcc5086a0f1b2bc8f6fc1552fdf77a6e62458c737