Skip to content
wasmer-config

Support multiple heterogeneous backends at the same time #1516

Sign in to view logs

Support multiple heterogeneous backends at the same time

Support multiple heterogeneous backends at the same time #1516

Triggered via pull request November 22, 2024 13:47
@xdoardoxdoardo
synchronize #5243
5198-cli-support-wasm_c_api-backends-together-with-native-ones
Status Success
Total duration 1m 51s
Artifacts –

wasmer-config.yaml

on: pull_request
Compile and Test
1m 41s
Compile and Test
Linting and Formatting
1m 20s
Linting and Formatting
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
Linting and Formatting
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Linting and Formatting
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Compile and Test
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Compile and Test
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/