Release #555
This run and associated checks have been archived and are scheduled for deletion.
Learn more about checks retention
release.yml
on: workflow_dispatch
Annotations
3 errors and 56 warnings
Doc generation
too many file operands
|
Doc generation
could not document `zenoh`
|
Doc generation
The process '/home/runner/.cargo/bin/cargo' failed with exit code 101
|
Code checks
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, 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/
|
Doc generation
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, 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/
|
Doc generation
virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
|
Doc generation
Target filter specified, but no targets matched. This is a no-op
|
Doc generation:
commons/zenoh-protocol/src/core/whatami.rs#L28
`&` without an explicit lifetime name cannot be used here
|
Doc generation:
commons/zenoh-protocol/src/core/whatami.rs#L29
`&` without an explicit lifetime name cannot be used here
|
Doc generation:
commons/zenoh-protocol/src/core/whatami.rs#L30
`&` without an explicit lifetime name cannot be used here
|
Doc generation:
commons/zenoh-protocol/src/core/resolution.rs#L30
`&` without an explicit lifetime name cannot be used here
|
Doc generation:
commons/zenoh-protocol/src/core/resolution.rs#L31
`&` without an explicit lifetime name cannot be used here
|
Doc generation:
commons/zenoh-protocol/src/core/resolution.rs#L32
`&` without an explicit lifetime name cannot be used here
|
Doc generation:
commons/zenoh-protocol/src/core/resolution.rs#L33
`&` without an explicit lifetime name cannot be used here
|
Doc generation
`zenoh-protocol` (lib) generated 7 warnings (run `cargo fix --lib -p zenoh-protocol` to apply 7 suggestions)
|
Build for x86_64-unknown-linux-musl on ubuntu-20.04
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, 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/
|
Build for aarch64-unknown-linux-musl on ubuntu-20.04
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, 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/
|
Build for x86_64-unknown-linux-gnu on ubuntu-20.04
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, 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/
|
Build for x86_64-unknown-linux-gnu on ubuntu-20.04
The next version of cargo-deb will add a "-1" suffix to versions.
|
Build for x86_64-unknown-linux-gnu on ubuntu-20.04
The next version of cargo-deb will add a "-1" suffix to versions.
|
Build for x86_64-unknown-linux-gnu on ubuntu-20.04
The next version of cargo-deb will add a "-1" suffix to versions.
|
Build for armv7-unknown-linux-gnueabihf on ubuntu-20.04
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, 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/
|
Build for armv7-unknown-linux-gnueabihf on ubuntu-20.04
The next version of cargo-deb will add a "-1" suffix to versions.
|
Build for armv7-unknown-linux-gnueabihf on ubuntu-20.04
The next version of cargo-deb will add a "-1" suffix to versions.
|
Build for armv7-unknown-linux-gnueabihf on ubuntu-20.04
spurious network error (3 tries remaining): failed to get successful HTTP response from `https://static.crates.io/crates/semver/semver-1.0.18.crate` (146.75.106.137), got 502
|
Build for armv7-unknown-linux-gnueabihf on ubuntu-20.04
spurious network error (3 tries remaining): failed to get successful HTTP response from `https://static.crates.io/crates/owo-colors/owo-colors-3.5.0.crate` (146.75.106.137), got 502
|
Build for armv7-unknown-linux-gnueabihf on ubuntu-20.04
spurious network error (3 tries remaining): failed to get successful HTTP response from `https://static.crates.io/crates/object/object-0.32.1.crate` (146.75.106.137), got 502
|
Build for armv7-unknown-linux-gnueabihf on ubuntu-20.04
spurious network error (3 tries remaining): failed to get successful HTTP response from `https://static.crates.io/crates/nix/nix-0.27.1.crate` (146.75.106.137), got 502
|
Build for armv7-unknown-linux-gnueabihf on ubuntu-20.04
spurious network error (3 tries remaining): failed to get successful HTTP response from `https://static.crates.io/crates/directories/directories-4.0.1.crate` (146.75.106.137), got 502
|
Build for armv7-unknown-linux-gnueabihf on ubuntu-20.04
spurious network error (3 tries remaining): failed to get successful HTTP response from `https://static.crates.io/crates/os_str_bytes/os_str_bytes-6.5.1.crate` (146.75.106.137), got 502
|
Build for armv7-unknown-linux-gnueabihf on ubuntu-20.04
spurious network error (3 tries remaining): failed to get successful HTTP response from `https://static.crates.io/crates/color-eyre/color-eyre-0.6.2.crate` (146.75.106.137), got 502
|
Build for armv7-unknown-linux-gnueabihf on ubuntu-20.04
spurious network error (3 tries remaining): failed to get successful HTTP response from `https://static.crates.io/crates/once_cell/once_cell-1.18.0.crate` (146.75.106.137), got 502
|
Build for armv7-unknown-linux-gnueabihf on ubuntu-20.04
spurious network error (3 tries remaining): failed to get successful HTTP response from `https://static.crates.io/crates/is_ci/is_ci-1.1.1.crate` (146.75.106.137), got 502
|
Build for armv7-unknown-linux-gnueabihf on ubuntu-20.04
spurious network error (3 tries remaining): failed to get successful HTTP response from `https://static.crates.io/crates/proc-macro-error/proc-macro-error-1.0.4.crate` (146.75.106.137), got 502
|
Build for armv7-unknown-linux-gnueabihf on ubuntu-20.04
The next version of cargo-deb will add a "-1" suffix to versions.
|
Build for aarch64-apple-darwin on macos-latest
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, 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/
|
Build for x86_64-apple-darwin on macos-latest
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, 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/
|
Build for arm-unknown-linux-gnueabi on ubuntu-20.04
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, 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/
|
Build for arm-unknown-linux-gnueabi on ubuntu-20.04
The next version of cargo-deb will add a "-1" suffix to versions.
|
Build for arm-unknown-linux-gnueabi on ubuntu-20.04
The next version of cargo-deb will add a "-1" suffix to versions.
|
Build for arm-unknown-linux-gnueabi on ubuntu-20.04
The next version of cargo-deb will add a "-1" suffix to versions.
|
Build for x86_64-pc-windows-msvc on windows-2019
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, 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/
|
Build for x86_64-pc-windows-msvc on windows-2019
spurious network error (3 tries remaining): failed to get successful HTTP response from `https://static.crates.io/crates/const_fn/const_fn-0.4.9.crate` (146.75.30.137), got 502
|
Build for x86_64-pc-windows-msvc on windows-2019
spurious network error (3 tries remaining): failed to get successful HTTP response from `https://static.crates.io/crates/const-oid/const-oid-0.9.4.crate` (146.75.30.137), got 502
|
Build for x86_64-pc-windows-msvc on windows-2019
spurious network error (3 tries remaining): failed to get successful HTTP response from `https://static.crates.io/crates/aes/aes-0.8.3.crate` (146.75.30.137), got 502
|
Build for x86_64-pc-windows-msvc on windows-2019
spurious network error (3 tries remaining): failed to get successful HTTP response from `https://static.crates.io/crates/aes-gcm/aes-gcm-0.8.0.crate` (146.75.30.137), got 502
|
Build for x86_64-pc-windows-msvc on windows-2019
spurious network error (3 tries remaining): failed to get successful HTTP response from `https://static.crates.io/crates/aes/aes-0.6.0.crate` (146.75.30.137), got 502
|
Build for x86_64-pc-windows-msvc on windows-2019
spurious network error (3 tries remaining): failed to get successful HTTP response from `https://static.crates.io/crates/aead/aead-0.3.2.crate` (146.75.30.137), got 502
|
Build for x86_64-pc-windows-msvc on windows-2019
spurious network error (3 tries remaining): failed to get successful HTTP response from `https://static.crates.io/crates/ipnet/ipnet-2.8.0.crate` (146.75.30.137), got 502
|
Build for x86_64-pc-windows-msvc on windows-2019
spurious network error (3 tries remaining): failed to get successful HTTP response from `https://static.crates.io/crates/inout/inout-0.1.3.crate` (146.75.30.137), got 502
|
Build for x86_64-pc-windows-msvc on windows-2019
spurious network error (3 tries remaining): failed to get successful HTTP response from `https://static.crates.io/crates/httpdate/httpdate-1.0.3.crate` (146.75.30.137), got 502
|
Build for aarch64-unknown-linux-gnu on ubuntu-20.04
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, 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/
|
Build for aarch64-unknown-linux-gnu on ubuntu-20.04
The next version of cargo-deb will add a "-1" suffix to versions.
|
Build for aarch64-unknown-linux-gnu on ubuntu-20.04
The next version of cargo-deb will add a "-1" suffix to versions.
|
Build for aarch64-unknown-linux-gnu on ubuntu-20.04
The next version of cargo-deb will add a "-1" suffix to versions.
|
Build for arm-unknown-linux-gnueabihf on ubuntu-20.04
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, 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/
|
Build for arm-unknown-linux-gnueabihf on ubuntu-20.04
The next version of cargo-deb will add a "-1" suffix to versions.
|
Build for arm-unknown-linux-gnueabihf on ubuntu-20.04
The next version of cargo-deb will add a "-1" suffix to versions.
|
Build for arm-unknown-linux-gnueabihf on ubuntu-20.04
The next version of cargo-deb will add a "-1" suffix to versions.
|
Artifacts
Produced during runtime
Name | Size | |
---|---|---|
aarch64-apple-darwin
Expired
|
7.4 MB |
|
aarch64-unknown-linux-gnu
Expired
|
14.9 MB |
|
aarch64-unknown-linux-musl
Expired
|
10.7 MB |
|
arm-unknown-linux-gnueabi
Expired
|
15 MB |
|
arm-unknown-linux-gnueabihf
Expired
|
15.2 MB |
|
armv7-unknown-linux-gnueabihf
Expired
|
14.9 MB |
|
x86_64-apple-darwin
Expired
|
7.93 MB |
|
x86_64-pc-windows-msvc
Expired
|
6.83 MB |
|
x86_64-unknown-linux-gnu
Expired
|
15.7 MB |
|
x86_64-unknown-linux-musl
Expired
|
11.1 MB |
|