Skip to content

Feature: add auto secure scheme support in binding-opcua (#1425) #2854

Feature: add auto secure scheme support in binding-opcua (#1425)

Feature: add auto secure scheme support in binding-opcua (#1425) #2854

Triggered via push September 24, 2025 08:30
Status Failure
Total duration 7m 18s
Artifacts

ci.yaml

on: push
eslint
1m 26s
eslint
Check version consistency of packages
10s
Check version consistency of packages
Check coding style
8s
Check coding style
Matrix: setup-and-test
Fit to window
Zoom out
Zoom in

Annotations

7 errors and 3 notices
Tests (windows-latest, Node 22.x)
Process completed with exit code 1.
Tests (macos-latest, Node 20.x)
The operation was canceled.
Tests (macos-latest, Node 20.x)
The strategy configuration was canceled because "setup-and-test.windows-latest_22_x" failed
Tests (macos-latest, Node 22.x)
The operation was canceled.
Tests (macos-latest, Node 22.x)
The strategy configuration was canceled because "setup-and-test.windows-latest_22_x" failed
Tests (macos-latest, Node 24.x)
The operation was canceled.
Tests (macos-latest, Node 24.x)
The strategy configuration was canceled because "setup-and-test.windows-latest_22_x" failed
Tests (windows-latest, Node 20.x)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Tests (windows-latest, Node 24.x)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Tests (windows-latest, Node 22.x)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677