ci(tests-ui): pin ComfyUI_devtools

[marawan206]

update the SHA in the tests-ui github actions to use the new ComfyUI_devtools commit

┆Issue is synchronized with this Notion page by Unito

[github-actions]

🎭 Playwright Test Results

Tests are starting...

⏰ Started at: 09/15/2025, 11:22:51 PM UTC

🚀 Running Tests

• 🧪 chromium: Running tests...
• 🧪 chromium-0.5x: Running tests...
• 🧪 chromium-2x: Running tests...
• 🧪 mobile-chrome: Running tests...

---

⏱️ Please wait while tests are running...

[christian-byrne]

This one as well:

ComfyUI_frontend/.github/workflows/test-ui.yaml

Line 35 in 48d0174

ref: 'd05fd48dd787a4192e16802d4244cfcc0e2f9684'

[DrJKL]

Is the default branch not on the latest version?

[christian-byrne]

Pinning just allows updating in specific order and better security, I guess.

[christian-byrne]

By "updating in specific order" I mean, if you change the devtools nodes and it's not pinned, CI in the frontend can start to unexpectedly fail until tests are changed (if necessary). Another reason for

• Merge ComfyUI-devtools and ComfyUI_frontend #4683

[christian-byrne]

This test case fails:

    Test timeout of 15000ms exceeded.

    Error: locator.click: Test timeout of 15000ms exceeded.
    Call log:
      - waiting for locator('.p-tree-node-content:has(> .tree-explorer-node-label:has(.tree-leaf .node-label:has-text("Remote Widget Node With Refresh Button and Control After Refresh")))').first()


      16 |     const nodeEntry = tab.getNode(nodeName).first()
      17 |     for (let i = 0; i < count; i++) {
    > 18 |       await nodeEntry.click()
         |                       ^
      19 |       await comfyPage.nextFrame()
      20 |     }
      21 |   }
        at addRemoteWidgetNode (/home/runner/work/ComfyUI_frontend/ComfyUI_frontend/ComfyUI_frontend/browser_tests/tests/remoteWidgets.spec.ts:18:23)
        at /home/runner/work/ComfyUI_frontend/ComfyUI_frontend/ComfyUI_frontend/browser_tests/tests/remoteWidgets.spec.ts:328:7

    Error Context: test-results/tests-remoteWidgets-Remote-c1324-sh-is-applied-after-refresh-chromium-retry3/error-context.md

  1 failed
    [chromium] › browser_tests/tests/remoteWidgets.spec.ts:306:5 › Remote COMBO Widget › Refresh Behavior › control_after_refresh is applied after refresh 

Likely will be fixed by

• RemoteWidgetNodeWithControlAfterRefresh node missing RETURN_TYPES ComfyUI_devtools#14

[DrJKL]

#5166