Skip to content

core: Add signal/timeout options to RunnableConfig #21

core: Add signal/timeout options to RunnableConfig

core: Add signal/timeout options to RunnableConfig #21

Triggered via pull request August 1, 2024 00:56
Status Failure
Total duration 57s
Artifacts

platform-compatibility.yml

on: pull_request
Matrix: platform-compatibility
Fit to window
Zoom out
Zoom in

Annotations

9 errors and 1 warning
platform-compatibility (ubuntu-latest)
'AbortSignal.any' is of type 'unknown'.
platform-compatibility (ubuntu-latest)
'AbortSignal.any' is of type 'unknown'.
platform-compatibility (ubuntu-latest)
'AbortSignal.any' is of type 'unknown'.
platform-compatibility (ubuntu-latest)
'AbortSignal.any' is of type 'unknown'.
platform-compatibility (ubuntu-latest)
Process completed with exit code 1.
platform-compatibility (windows-latest)
The job was canceled because "ubuntu-latest" failed.
platform-compatibility (windows-latest)
The operation was canceled.
platform-compatibility (macos-latest)
The job was canceled because "ubuntu-latest" failed.
platform-compatibility (macos-latest)
The operation was canceled.
platform-compatibility (ubuntu-latest)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/setup-node@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/