Skip to content

Add tokio feature flag for easier integration with the async runtime #355

Add tokio feature flag for easier integration with the async runtime

Add tokio feature flag for easier integration with the async runtime #355

Triggered via pull request October 30, 2024 19:49
Status Failure
Total duration 1m 1s
Artifacts

ci.yml

on: pull_request
Matrix: protocol
Matrix: proxy
Fit to window
Zoom out
Zoom in

Annotations

11 errors and 3 warnings
protocol (stable)
Process completed with exit code 101.
protocol (nightly)
The job was canceled because "stable" failed.
protocol (nightly)
Process completed with exit code 101.
protocol (beta)
The job was canceled because "stable" failed.
protocol (beta)
Process completed with exit code 101.
protocol (1.63.0)
The job was canceled because "stable" failed.
protocol (1.63.0)
The operation was canceled.
proxy (nightly)
Process completed with exit code 101.
proxy (beta)
Process completed with exit code 101.
proxy (stable)
The job was canceled because "nightly" failed.
proxy (stable)
Process completed with exit code 101.
protocol (stable)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
proxy (nightly)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
proxy (beta)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/