fix(core): don't show warning about max allocation groups if tracing not enabled #34155
Triggered via pull request
September 18, 2023 14:39
tobz
Status
Success
Total duration
38m 12s
Artifacts
–
This run and associated checks have been archived and are scheduled for deletion.
Learn more about checks retention
Annotations
11 warnings
|
changes / source
'ref' input parameter is ignored when 'base' is set to HEAD
|
|
changes / source
'base' input parameter is ignored when action is triggered by pull request event
|
|
Checks
/home/runner/work/vector/vector/Cargo.toml: unused manifest key: patch.crates-io.openssl-src.ref
|
|
Checks
output filename collision.
|
|
Checks
output filename collision.
|
|
Checks
output filename collision.
|
|
Checks
output filename collision.
|
|
Checks
output filename collision.
|
|
Checks
/home/runner/work/vector/vector/Cargo.toml: unused manifest key: patch.crates-io.openssl-src.ref
|
|
Checks
/home/runner/work/vector/vector/Cargo.toml: unused manifest key: patch.crates-io.openssl-src.ref
|
|
Checks
ignoring unknown configuration keys in config file /home/runner/work/vector/vector/.config/nextest.toml: profile.default.junit.store-failure-output
|