Skip to content

Marker traits (#6871) #3380

Marker traits (#6871)

Marker traits (#6871) #3380

Triggered via push February 7, 2025 03:26
Status Success
Total duration 16m 25s
Artifacts

gh-pages.yml

on: push
Fit to window
Zoom out
Zoom in

Annotations

23 warnings
deploy
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/
deploy
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/
deploy
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/
deploy
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/
deploy
package `parity-scale-codec v3.7.0` in Cargo.lock is yanked in registry `crates-io`, consider running without --locked
deploy
package `ruzstd v0.7.2` in Cargo.lock is yanked in registry `crates-io`, consider running without --locked
deploy
package `sdd v3.0.4` in Cargo.lock is yanked in registry `crates-io`, consider running without --locked
deploy
spurious network error (3 tries remaining): failed to get successful HTTP response from `https://index.crates.io/se/ri/serial_test` (18.245.46.85), got 503
deploy
spurious network error (3 tries remaining): failed to get successful HTTP response from `https://index.crates.io/sm/aw/smawk` (18.245.46.85), got 503
deploy
spurious network error (3 tries remaining): failed to get successful HTTP response from `https://index.crates.io/ic/u_/icu_locid` (18.245.46.85), got 503
deploy
spurious network error (3 tries remaining): failed to get successful HTTP response from `https://index.crates.io/ri/ng/ring` (18.245.46.85), got 503
deploy
spurious network error (3 tries remaining): failed to get successful HTTP response from `https://index.crates.io/sc/he/schemafy_core` (18.245.46.85), got 503
deploy
spurious network error (3 tries remaining): failed to get successful HTTP response from `https://index.crates.io/2/h2` (18.245.46.85), got 503
deploy
spurious network error (3 tries remaining): failed to get successful HTTP response from `https://index.crates.io/mi/ni/miniz_oxide` (18.245.46.85), got 503
deploy
package `parity-scale-codec v3.7.0` in Cargo.lock is yanked in registry `crates-io`, consider running without --locked
deploy
package `ruzstd v0.7.2` in Cargo.lock is yanked in registry `crates-io`, consider running without --locked
deploy
package `sdd v3.0.4` in Cargo.lock is yanked in registry `crates-io`, consider running without --locked
deploy
The `save-state` 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/
deploy
The `save-state` 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/
deploy
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/
deploy
package `parity-scale-codec v3.7.0` in Cargo.lock is yanked in registry `crates-io`, consider running without --locked
deploy
package `ruzstd v0.7.2` in Cargo.lock is yanked in registry `crates-io`, consider running without --locked
deploy
package `sdd v3.0.4` in Cargo.lock is yanked in registry `crates-io`, consider running without --locked