Skip to content

Update polling requirement from 2.8.0 to 3.2.0 #693

Update polling requirement from 2.8.0 to 3.2.0

Update polling requirement from 2.8.0 to 3.2.0 #693

Triggered via push October 3, 2023 03:23
Status Failure
Total duration 3m 39s
Artifacts

ci.yml

on: push
Run cargo fmt and cargo clippy
46s
Run cargo fmt and cargo clippy
Matrix: linux
Matrix: macos
Matrix: windows
Fit to window
Zoom out
Zoom in

Annotations

134 errors and 60 warnings
Run cargo fmt and cargo clippy
The process '/home/runner/.cargo/bin/cargo' failed with exit code 101
Test stable on ubuntu-latest: open-coroutine-core/src/event_loop/selector.rs#L101
the trait bound `i32: AsFd` is not satisfied
Test stable on ubuntu-latest: open-coroutine-core/src/event_loop/selector.rs#L178
the trait bound `i32: AsFd` is not satisfied
Test stable on ubuntu-latest
Process completed with exit code 101.
Test stable on ubuntu-latest: open-coroutine-core/src/event_loop/selector.rs#L101
the trait bound `i32: AsFd` is not satisfied
Test stable on ubuntu-latest: open-coroutine-core/src/event_loop/selector.rs#L178
the trait bound `i32: AsFd` is not satisfied
Test stable on ubuntu-latest
Process completed with exit code 101.
Test stable on ubuntu-latest: open-coroutine-core/src/event_loop/selector.rs#L101
the trait bound `i32: AsFd` is not satisfied
Test stable on ubuntu-latest: open-coroutine-core/src/event_loop/selector.rs#L178
the trait bound `i32: AsFd` is not satisfied
Test stable on ubuntu-latest
Process completed with exit code 101.
Test stable on ubuntu-latest: open-coroutine-core/src/event_loop/selector.rs#L101
the trait bound `i32: AsFd` is not satisfied
Test stable on ubuntu-latest: open-coroutine-core/src/event_loop/selector.rs#L178
the trait bound `i32: AsFd` is not satisfied
Test stable on ubuntu-latest
could not compile `open-coroutine-core` (lib) due to 3 previous errors
Test stable on ubuntu-latest
Process completed with exit code 101.
Test stable on ubuntu-latest
The process '/home/runner/.cargo/bin/cargo' failed with exit code 101
Test stable on ubuntu-latest: open-coroutine-core/src/event_loop/selector.rs#L101
the trait bound `i32: AsFd` is not satisfied
Test stable on ubuntu-latest: open-coroutine-core/src/event_loop/selector.rs#L178
the trait bound `i32: AsFd` is not satisfied
Test stable on ubuntu-latest
Process completed with exit code 101.
Test stable on ubuntu-latest: open-coroutine-core/src/event_loop/selector.rs#L101
the trait bound `i32: AsFd` is not satisfied
Test stable on ubuntu-latest: open-coroutine-core/src/event_loop/selector.rs#L178
the trait bound `i32: AsFd` is not satisfied
Test stable on ubuntu-latest
could not compile `open-coroutine-core` (lib) due to 3 previous errors
Test stable on ubuntu-latest
Process completed with exit code 101.
Test stable on ubuntu-latest: open-coroutine-core/src/event_loop/selector.rs#L101
the trait bound `i32: AsFd` is not satisfied
Test stable on ubuntu-latest: open-coroutine-core/src/event_loop/selector.rs#L178
the trait bound `i32: AsFd` is not satisfied
Test stable on ubuntu-latest
Process completed with exit code 101.
Test nightly on ubuntu-latest: open-coroutine-core/src/event_loop/selector.rs#L101
the trait bound `i32: AsFd` is not satisfied
Test nightly on ubuntu-latest: open-coroutine-core/src/event_loop/selector.rs#L178
the trait bound `i32: AsFd` is not satisfied
Test nightly on ubuntu-latest
could not compile `open-coroutine-core` (lib) due to 3 previous errors
Test nightly on ubuntu-latest
Process completed with exit code 101.
Test nightly on ubuntu-latest: open-coroutine-core/src/event_loop/selector.rs#L101
the trait bound `i32: AsFd` is not satisfied
Test nightly on ubuntu-latest: open-coroutine-core/src/event_loop/selector.rs#L178
the trait bound `i32: AsFd` is not satisfied
Test nightly on ubuntu-latest
Process completed with exit code 101.
Test nightly on ubuntu-latest: open-coroutine-core/src/event_loop/selector.rs#L101
the trait bound `i32: AsFd` is not satisfied
Test nightly on ubuntu-latest: open-coroutine-core/src/event_loop/selector.rs#L178
the trait bound `i32: AsFd` is not satisfied
Test nightly on ubuntu-latest
could not compile `open-coroutine-core` (lib) due to 3 previous errors
Test nightly on ubuntu-latest
Process completed with exit code 101.
Test nightly on ubuntu-latest
The process '/home/runner/.cargo/bin/cargo' failed with exit code 101
Test nightly on ubuntu-latest: open-coroutine-core/src/event_loop/selector.rs#L101
the trait bound `i32: AsFd` is not satisfied
Test nightly on ubuntu-latest: open-coroutine-core/src/event_loop/selector.rs#L178
the trait bound `i32: AsFd` is not satisfied
Test nightly on ubuntu-latest
could not compile `open-coroutine-core` (lib) due to 3 previous errors
Test nightly on ubuntu-latest
Process completed with exit code 101.
Test nightly on ubuntu-latest: open-coroutine-core/src/event_loop/selector.rs#L101
the trait bound `i32: AsFd` is not satisfied
Test nightly on ubuntu-latest: open-coroutine-core/src/event_loop/selector.rs#L178
the trait bound `i32: AsFd` is not satisfied
Test nightly on ubuntu-latest
Process completed with exit code 101.
Test nightly on ubuntu-latest: open-coroutine-core/src/event_loop/selector.rs#L101
the trait bound `i32: AsFd` is not satisfied
Test nightly on ubuntu-latest: open-coroutine-core/src/event_loop/selector.rs#L178
the trait bound `i32: AsFd` is not satisfied
Test nightly on ubuntu-latest
Process completed with exit code 101.
Test nightly on ubuntu-latest: open-coroutine-core/src/event_loop/selector.rs#L101
the trait bound `i32: AsFd` is not satisfied
Test nightly on ubuntu-latest: open-coroutine-core/src/event_loop/selector.rs#L178
the trait bound `i32: AsFd` is not satisfied
Test nightly on ubuntu-latest
Process completed with exit code 101.
Test stable on macOS-latest
The process '/Users/runner/.cargo/bin/cargo' failed with exit code 101
Test stable on macOS-latest: open-coroutine-core/src/event_loop/selector.rs#L101
the trait bound `i32: AsFd` is not satisfied
Test stable on macOS-latest: open-coroutine-core/src/event_loop/selector.rs#L178
the trait bound `i32: AsFd` is not satisfied
Test stable on macOS-latest
Process completed with exit code 101.
Test stable on macOS-latest: open-coroutine-core/src/event_loop/selector.rs#L101
the trait bound `i32: AsFd` is not satisfied
Test stable on macOS-latest: open-coroutine-core/src/event_loop/selector.rs#L178
the trait bound `i32: AsFd` is not satisfied
Test stable on macOS-latest
Process completed with exit code 101.
Test stable on macOS-latest: open-coroutine-core/src/event_loop/selector.rs#L101
the trait bound `i32: AsFd` is not satisfied
Test stable on macOS-latest: open-coroutine-core/src/event_loop/selector.rs#L178
the trait bound `i32: AsFd` is not satisfied
Test stable on macOS-latest
Process completed with exit code 101.
Test stable on macOS-latest: open-coroutine-core/src/event_loop/selector.rs#L101
the trait bound `i32: AsFd` is not satisfied
Test stable on macOS-latest: open-coroutine-core/src/event_loop/selector.rs#L178
the trait bound `i32: AsFd` is not satisfied
Test stable on macOS-latest
Process completed with exit code 101.
Test stable on macOS-latest: open-coroutine-core/src/event_loop/selector.rs#L101
the trait bound `i32: AsFd` is not satisfied
Test stable on macOS-latest: open-coroutine-core/src/event_loop/selector.rs#L178
the trait bound `i32: AsFd` is not satisfied
Test stable on macOS-latest
Process completed with exit code 101.
Test stable on macOS-latest: open-coroutine-core/src/event_loop/selector.rs#L101
the trait bound `i32: AsFd` is not satisfied
Test stable on macOS-latest: open-coroutine-core/src/event_loop/selector.rs#L178
the trait bound `i32: AsFd` is not satisfied
Test stable on macOS-latest
could not compile `open-coroutine-core` (lib) due to 3 previous errors
Test stable on macOS-latest
Process completed with exit code 101.
Test stable on macOS-latest: open-coroutine-core/src/event_loop/selector.rs#L101
the trait bound `i32: AsFd` is not satisfied
Test stable on macOS-latest: open-coroutine-core/src/event_loop/selector.rs#L178
the trait bound `i32: AsFd` is not satisfied
Test stable on macOS-latest
could not compile `open-coroutine-core` (lib) due to 3 previous errors
Test stable on macOS-latest
Process completed with exit code 101.
Test nightly on macOS-latest: open-coroutine-core/src/event_loop/selector.rs#L101
the trait bound `i32: AsFd` is not satisfied
Test nightly on macOS-latest: open-coroutine-core/src/event_loop/selector.rs#L178
the trait bound `i32: AsFd` is not satisfied
Test nightly on macOS-latest
could not compile `open-coroutine-core` (lib) due to 3 previous errors
Test nightly on macOS-latest
Process completed with exit code 101.
Test nightly on macOS-latest: open-coroutine-core/src/event_loop/selector.rs#L101
the trait bound `i32: AsFd` is not satisfied
Test nightly on macOS-latest: open-coroutine-core/src/event_loop/selector.rs#L178
the trait bound `i32: AsFd` is not satisfied
Test nightly on macOS-latest
Process completed with exit code 101.
Test nightly on macOS-latest
The process '/Users/runner/.cargo/bin/cargo' failed with exit code 101
Test nightly on macOS-latest: open-coroutine-core/src/event_loop/selector.rs#L101
the trait bound `i32: AsFd` is not satisfied
Test nightly on macOS-latest: open-coroutine-core/src/event_loop/selector.rs#L178
the trait bound `i32: AsFd` is not satisfied
Test nightly on macOS-latest
Process completed with exit code 101.
Test nightly on macOS-latest: open-coroutine-core/src/event_loop/selector.rs#L101
the trait bound `i32: AsFd` is not satisfied
Test nightly on macOS-latest: open-coroutine-core/src/event_loop/selector.rs#L178
the trait bound `i32: AsFd` is not satisfied
Test nightly on macOS-latest
Process completed with exit code 101.
Test nightly on macOS-latest: open-coroutine-core/src/event_loop/selector.rs#L101
the trait bound `i32: AsFd` is not satisfied
Test nightly on macOS-latest: open-coroutine-core/src/event_loop/selector.rs#L178
the trait bound `i32: AsFd` is not satisfied
Test nightly on macOS-latest
could not compile `open-coroutine-core` (lib) due to 3 previous errors
Test nightly on macOS-latest
Process completed with exit code 101.
Test nightly on macOS-latest: open-coroutine-core/src/event_loop/selector.rs#L101
the trait bound `i32: AsFd` is not satisfied
Test nightly on macOS-latest: open-coroutine-core/src/event_loop/selector.rs#L178
the trait bound `i32: AsFd` is not satisfied
Test nightly on macOS-latest
Process completed with exit code 101.
Test nightly on macOS-latest: open-coroutine-core/src/event_loop/selector.rs#L101
the trait bound `i32: AsFd` is not satisfied
Test nightly on macOS-latest: open-coroutine-core/src/event_loop/selector.rs#L178
the trait bound `i32: AsFd` is not satisfied
Test nightly on macOS-latest
could not compile `open-coroutine-core` (lib) due to 3 previous errors
Test nightly on macOS-latest
Process completed with exit code 101.
Test nightly-x86_64-pc-windows-gnu on windows-latest
Process completed with exit code 1.
Test nightly-x86_64-pc-windows-gnu on windows-latest
Process completed with exit code 1.
Test nightly-x86_64-pc-windows-gnu on windows-latest
Process completed with exit code 1.
Test nightly-x86_64-pc-windows-gnu on windows-latest
The process 'C:\Users\runneradmin\.cargo\bin\cargo.exe' failed with exit code 101
Test nightly-x86_64-pc-windows-gnu on windows-latest
Process completed with exit code 1.
Test nightly-x86_64-pc-windows-gnu on windows-latest
Process completed with exit code 1.
Test nightly-x86_64-pc-windows-gnu on windows-latest
Process completed with exit code 1.
Run cargo fmt and cargo clippy
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions-rs/toolchain@v1, actions-rs/cargo@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Run cargo fmt and cargo clippy
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Run cargo fmt and cargo clippy
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Run cargo fmt and cargo clippy
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Run cargo fmt and cargo clippy
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Test stable on ubuntu-latest
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions-rs/toolchain@v1, actions-rs/cargo@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Test stable on ubuntu-latest
some crates are on edition 2021 which defaults to `resolver = "2"`, but virtual workspaces default to `resolver = "1"`
Test stable on ubuntu-latest
some crates are on edition 2021 which defaults to `resolver = "2"`, but virtual workspaces default to `resolver = "1"`
Test stable on ubuntu-latest
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Test stable on ubuntu-latest
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Test stable on ubuntu-latest
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Test stable on ubuntu-latest
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Test stable on ubuntu-latest
some crates are on edition 2021 which defaults to `resolver = "2"`, but virtual workspaces default to `resolver = "1"`
Test stable on ubuntu-latest
some crates are on edition 2021 which defaults to `resolver = "2"`, but virtual workspaces default to `resolver = "1"`
Test stable on ubuntu-latest
some crates are on edition 2021 which defaults to `resolver = "2"`, but virtual workspaces default to `resolver = "1"`
Test stable on ubuntu-latest
some crates are on edition 2021 which defaults to `resolver = "2"`, but virtual workspaces default to `resolver = "1"`
Test stable on ubuntu-latest
some crates are on edition 2021 which defaults to `resolver = "2"`, but virtual workspaces default to `resolver = "1"`
Test stable on ubuntu-latest
some crates are on edition 2021 which defaults to `resolver = "2"`, but virtual workspaces default to `resolver = "1"`
Test nightly on ubuntu-latest
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions-rs/toolchain@v1, actions-rs/cargo@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Test nightly on ubuntu-latest
virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
Test nightly on ubuntu-latest
virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
Test nightly on ubuntu-latest
virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
Test nightly on ubuntu-latest
virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
Test nightly on ubuntu-latest
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Test nightly on ubuntu-latest
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Test nightly on ubuntu-latest
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Test nightly on ubuntu-latest
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Test nightly on ubuntu-latest
virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
Test nightly on ubuntu-latest
virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
Test nightly on ubuntu-latest
virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
Test nightly on ubuntu-latest
virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
Test stable on macOS-latest
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions-rs/toolchain@v1, actions-rs/cargo@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Test stable on macOS-latest
some crates are on edition 2021 which defaults to `resolver = "2"`, but virtual workspaces default to `resolver = "1"`
Test stable on macOS-latest
some crates are on edition 2021 which defaults to `resolver = "2"`, but virtual workspaces default to `resolver = "1"`
Test stable on macOS-latest
some crates are on edition 2021 which defaults to `resolver = "2"`, but virtual workspaces default to `resolver = "1"`
Test stable on macOS-latest
some crates are on edition 2021 which defaults to `resolver = "2"`, but virtual workspaces default to `resolver = "1"`
Test stable on macOS-latest
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Test stable on macOS-latest
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Test stable on macOS-latest
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Test stable on macOS-latest
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Test stable on macOS-latest
some crates are on edition 2021 which defaults to `resolver = "2"`, but virtual workspaces default to `resolver = "1"`
Test stable on macOS-latest
some crates are on edition 2021 which defaults to `resolver = "2"`, but virtual workspaces default to `resolver = "1"`
Test stable on macOS-latest
some crates are on edition 2021 which defaults to `resolver = "2"`, but virtual workspaces default to `resolver = "1"`
Test nightly on macOS-latest
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions-rs/toolchain@v1, actions-rs/cargo@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Test nightly on macOS-latest
virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
Test nightly on macOS-latest
virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
Test nightly on macOS-latest
virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
Test nightly on macOS-latest
virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
Test nightly on macOS-latest
virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
Test nightly on macOS-latest
virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
Test nightly on macOS-latest
virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
Test nightly on macOS-latest
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Test nightly on macOS-latest
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Test nightly on macOS-latest
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Test nightly on macOS-latest
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Test nightly-x86_64-pc-windows-gnu on windows-latest
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions-rs/toolchain@v1, actions-rs/cargo@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Test nightly-x86_64-pc-windows-gnu on windows-latest
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Test nightly-x86_64-pc-windows-gnu on windows-latest
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Test nightly-x86_64-pc-windows-gnu on windows-latest
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Test nightly-x86_64-pc-windows-gnu on windows-latest
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/