Skip to content

Fixed adding provider from file bug #1685

Fixed adding provider from file bug

Fixed adding provider from file bug #1685

Triggered via pull request June 21, 2023 00:12
Status Failure
Total duration 18m 54s
Artifacts
This run and associated checks have been archived and are scheduled for deletion. Learn more about checks retention

host_core.yml

on: pull_request
Matrix: Build and test
Fit to window
Zoom out
Zoom in

Annotations

12 errors and 18 warnings
Build and test (windows-2019, 1.14.3, 25)
Process completed with exit code 1.
Build and test (windows-2019, 1.14.3, 25)
Command failed: cargo metadata --all-features --format-version 1
Build and test (windows-2019, 1.14.3, 25)
error: could not find `Cargo.toml` in `D:\a\wasmcloud-otp\wasmcloud-otp` or any parent directory
Build and test (windows-2019, 1.14.3, 25)
Error: ENOENT: no such file or directory, opendir 'D:\a\wasmcloud-otp\wasmcloud-otp\target'
Build and test (windows-2019, 1.14.3, 25)
Error: ENOENT: no such file or directory, opendir 'C:\Users\runneradmin\.cargo\registry\index'
Build and test (ubuntu-20.04, 1.14.3, 25)
test Performing standard operations on actors can invoke an actor after stopping all instances and restarting (HostCore.ActorsTest)
Build and test (ubuntu-20.04, 1.14.3, 25)
Process completed with exit code 2.
Build and test (ubuntu-20.04, 1.14.3, 25)
Process completed with exit code 14.
Build and test (macos-11, 1.14.3, 25)
Command failed: cargo metadata --all-features --format-version 1
Build and test (macos-11, 1.14.3, 25)
error: could not find `Cargo.toml` in `/Users/runner/work/wasmcloud-otp/wasmcloud-otp` or any parent directory
Build and test (macos-11, 1.14.3, 25)
Error: ENOENT: no such file or directory, opendir '/Users/runner/work/wasmcloud-otp/wasmcloud-otp/target'
Build and test (macos-11, 1.14.3, 25)
Process completed with exit code 14.
Build and test (windows-2019, 1.14.3, 25)
Node.js 12 actions are deprecated. Please update the following actions to use Node.js 16: actions/cache@v2. For more information see: https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/.
Build and test (ubuntu-20.04, 1.14.3, 25)
Node.js 12 actions are deprecated. Please update the following actions to use Node.js 16: actions/cache@v2. For more information see: https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/.
Build and test (ubuntu-20.04, 1.14.3, 25)
unused alias ActorSupervisor
Build and test (ubuntu-20.04, 1.14.3, 25)
unused alias JetstreamClient
Build and test (ubuntu-20.04, 1.14.3, 25)
unused alias Native
Build and test (ubuntu-20.04, 1.14.3, 25)
unused alias VirtualHost
Build and test (ubuntu-20.04, 1.14.3, 25)
variable "seed" is unused (if the variable is not meant to be used, prefix it with an underscore)
Build and test (ubuntu-20.04, 1.14.3, 25)
Nested modules could be aliased at the top of the invoking module.
Build and test (ubuntu-20.04, 1.14.3, 25)
Nested modules could be aliased at the top of the invoking module.
Build and test (ubuntu-20.04, 1.14.3, 25)
Nested modules could be aliased at the top of the invoking module.
Build and test (ubuntu-20.04, 1.14.3, 25)
Nested modules could be aliased at the top of the invoking module.
Build and test (ubuntu-20.04, 1.14.3, 25)
Nested modules could be aliased at the top of the invoking module.
Build and test (ubuntu-20.04, 1.14.3, 25)
Nested modules could be aliased at the top of the invoking module.
Build and test (ubuntu-20.04, 1.14.3, 25)
Nested modules could be aliased at the top of the invoking module.
Build and test (ubuntu-20.04, 1.14.3, 25)
Nested modules could be aliased at the top of the invoking module.
Build and test (ubuntu-20.04, 1.14.3, 25)
Nested modules could be aliased at the top of the invoking module.
Build and test (ubuntu-20.04, 1.14.3, 25)
Nested modules could be aliased at the top of the invoking module.
Build and test (macos-11, 1.14.3, 25)
Node.js 12 actions are deprecated. Please update the following actions to use Node.js 16: actions/cache@v2. For more information see: https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/.