Skip to content
Continuous integration

Beginning of the OTLP generator, example usage of the OTel sdk #3460

Sign in to view logs

Beginning of the OTLP generator, example usage of the OTel sdk

Beginning of the OTLP generator, example usage of the OTel sdk #3460

Triggered via pull request November 12, 2024 00:40
@dustmopdustmop
opened #1106
wip-otlp-generator
Status Failure
Total duration 5m 57s
Artifacts –

ci.yml

on: pull_request
cargo-deny
40s
cargo-deny
Test Suite
2m 29s
Test Suite
Integration Tests
2m 28s
Integration Tests
buf
9s
buf
actionlint
6s
actionlint
action-sha-pin-check
36s
action-sha-pin-check
Matrix: Kani Proofs
Matrix: Loom Proofs
Matrix: Rust Actions (Check/Fmt/Clippy)
Fit to window
Zoom out
Zoom in

Annotations

23 errors and 2 warnings
Rust Actions (Check/Fmt/Clippy) (ubuntu-latest): lading/src/generator/otlp.rs#L53
field `shutdown` is never read
Rust Actions (Check/Fmt/Clippy) (ubuntu-latest): lading/src/generator/otlp.rs#L57
used `unwrap()` on a `Result` value
Rust Actions (Check/Fmt/Clippy) (ubuntu-latest): lading/src/generator/otlp.rs#L89
this argument is passed by value, but not consumed in the function body
Rust Actions (Check/Fmt/Clippy) (ubuntu-latest): lading/src/generator/otlp.rs#L222
unneeded `return` statement
Rust Actions (Check/Fmt/Clippy) (ubuntu-latest): lading/src/generator/otlp.rs#L223
unneeded `return` statement
Rust Actions (Check/Fmt/Clippy) (ubuntu-latest): lading/src/generator/otlp.rs#L129
consider adding a `;` to the last statement for consistent formatting
Rust Actions (Check/Fmt/Clippy) (ubuntu-latest): lading/src/generator/otlp.rs#L157
consider adding a `;` to the last statement for consistent formatting
Rust Actions (Check/Fmt/Clippy) (ubuntu-latest): lading/src/generator/otlp.rs#L208
consider adding a `;` to the last statement for consistent formatting
Rust Actions (Check/Fmt/Clippy) (ubuntu-latest): lading/src/generator/otlp.rs#L222
matching over `()` is more explicit
Rust Actions (Check/Fmt/Clippy) (ubuntu-latest): lading/src/generator/otlp.rs#L105
unused `async` for function with no await statements
Rust Actions (Check/Fmt/Clippy) (macos-latest): lading/src/generator/otlp.rs#L53
field `shutdown` is never read
Rust Actions (Check/Fmt/Clippy) (macos-latest): lading/src/generator/otlp.rs#L57
used `unwrap()` on a `Result` value
Rust Actions (Check/Fmt/Clippy) (macos-latest): lading/src/generator/otlp.rs#L89
this argument is passed by value, but not consumed in the function body
Rust Actions (Check/Fmt/Clippy) (macos-latest): lading/src/generator/otlp.rs#L222
unneeded `return` statement
Rust Actions (Check/Fmt/Clippy) (macos-latest): lading/src/generator/otlp.rs#L223
unneeded `return` statement
Rust Actions (Check/Fmt/Clippy) (macos-latest): lading/src/generator/otlp.rs#L129
consider adding a `;` to the last statement for consistent formatting
Rust Actions (Check/Fmt/Clippy) (macos-latest): lading/src/generator/otlp.rs#L157
consider adding a `;` to the last statement for consistent formatting
Rust Actions (Check/Fmt/Clippy) (macos-latest): lading/src/generator/otlp.rs#L208
consider adding a `;` to the last statement for consistent formatting
Rust Actions (Check/Fmt/Clippy) (macos-latest): lading/src/generator/otlp.rs#L222
matching over `()` is more explicit
Rust Actions (Check/Fmt/Clippy) (macos-latest): lading/src/generator/otlp.rs#L105
unused `async` for function with no await statements
Integration Tests
Process completed with exit code 101.
Test Suite: lading/src/generator/otlp.rs#L53
field `shutdown` is never read
Test Suite
Process completed with exit code 101.
buf
No github_token supplied, API requests will be subject to stricter rate limiting
Rust Actions (Check/Fmt/Clippy) (macos-latest)
macOS's Gatekeeper has been disabled for this Cask