Skip to content
This repository has been archived by the owner on Oct 25, 2024. It is now read-only.

enhancement: transparently add internal types for GraphQL connection specification #4931

enhancement: transparently add internal types for GraphQL connection specification

enhancement: transparently add internal types for GraphQL connection specification #4931

Triggered via pull request October 10, 2023 18:29
Status Failure
Total duration 16m 23s
Artifacts
This run and associated checks have been archived and are scheduled for deletion. Learn more about checks retention

ci.yml

on: pull_request
set-env-vars
3s
set-env-vars
docs-test  /  Check Links
1m 5s
docs-test / Check Links
docs-test  /  Markdown Lint
11s
docs-test / Markdown Lint
docs-test  /  Check SUMMARY & Folders
6s
docs-test / Check SUMMARY & Folders
cancel-previous-runs
5s
cancel-previous-runs
cargo-fmt-check
14s
cargo-fmt-check
cargo-toml-fmt-check
13s
cargo-toml-fmt-check
publish-docker-image
0s
publish-docker-image
publish
0s
publish
Matrix: publish-fuel-indexer-binaries
cargo-clippy-no-default-features
2m 0s
cargo-clippy-no-default-features
cargo-clippy-all-features-all-targets
4m 59s
cargo-clippy-all-features-all-targets
unit-tests
4m 20s
unit-tests
integration-tests
13m 43s
integration-tests
validation-complete
4s
validation-complete
notify-slack-on-failure
1s
notify-slack-on-failure
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 1 warning
unit-tests
Process completed with exit code 101.
integration-tests
Process completed with exit code 101.
cancel-previous-runs
The following actions uses node12 which is deprecated and will be forced to run on node16: styfle/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/