Skip to content

Add PartiQL DDL Extension (#468) #131

Add PartiQL DDL Extension (#468)

Add PartiQL DDL Extension (#468) #131

Triggered via push June 24, 2024 19:13
Status Success
Total duration 12m 1s
Artifacts

benchmark.yml

on: push
Performance regression check
11m 53s
Performance regression check
Fit to window
Zoom out
Zoom in

Annotations

18 warnings
deny(rust_2018_idioms) is ignored unless specified at crate level: partiql/src/subquery_tests.rs#L1
warning: deny(rust_2018_idioms) is ignored unless specified at crate level --> partiql/src/subquery_tests.rs:1:9 | 1 | #![deny(rust_2018_idioms)] | ^^^^^^^^^^^^^^^^ | = note: `#[warn(unused_attributes)]` on by default
field `result` is never read: partiql-conformance-test-generator/src/schema.rs#L164
warning: field `result` is never read --> partiql-conformance-test-generator/src/schema.rs:164:13 | 163 | pub struct EvaluationFailAssertion { | ----------------------- field in this struct 164 | pub result: String, | ^^^^^^ | = note: `EvaluationFailAssertion` has derived impls for the traits `Clone` and `Debug`, but these are intentionally ignored during dead code analysis
field `result` is never read: partiql-conformance-test-generator/src/schema.rs#L157
warning: field `result` is never read --> partiql-conformance-test-generator/src/schema.rs:157:13 | 156 | pub struct EvaluationSuccessAssertion { | -------------------------- field in this struct 157 | pub result: String, | ^^^^^^ | = note: `EvaluationSuccessAssertion` has derived impls for the traits `Clone` and `Debug`, but these are intentionally ignored during dead code analysis
field `result` is never read: partiql-conformance-test-generator/src/schema.rs#L152
warning: field `result` is never read --> partiql-conformance-test-generator/src/schema.rs:152:13 | 151 | pub struct StaticAnalysisFailAssertion { | --------------------------- field in this struct 152 | pub result: String, | ^^^^^^ | = note: `StaticAnalysisFailAssertion` has derived impls for the traits `Clone` and `Debug`, but these are intentionally ignored during dead code analysis
field `result` is never read: partiql-conformance-test-generator/src/schema.rs#L147
warning: field `result` is never read --> partiql-conformance-test-generator/src/schema.rs:147:13 | 146 | pub struct SyntaxFailAssertion { | ------------------- field in this struct 147 | pub result: String, | ^^^^^^ | = note: `SyntaxFailAssertion` has derived impls for the traits `Clone` and `Debug`, but these are intentionally ignored during dead code analysis
field `result` is never read: partiql-conformance-test-generator/src/schema.rs#L142
warning: field `result` is never read --> partiql-conformance-test-generator/src/schema.rs:142:13 | 141 | pub struct SyntaxSuccessAssertion { | ---------------------- field in this struct 142 | pub result: String, | ^^^^^^ | = note: `SyntaxSuccessAssertion` has derived impls for the traits `Clone` and `Debug`, but these are intentionally ignored during dead code analysis
field `0` is never read: partiql-conformance-test-generator/src/schema.rs#L75
warning: field `0` is never read --> partiql-conformance-test-generator/src/schema.rs:75:28 | 75 | StaticAnalysisFail(StaticAnalysisFailAssertion), | ------------------ ^^^^^^^^^^^^^^^^^^^^^^^^^^^ | | | field in this variant | help: consider changing the field to be of unit type to suppress this warning while preserving the field numbering, or remove the field | 75 | StaticAnalysisFail(()), | ~~
field `0` is never read: partiql-conformance-test-generator/src/schema.rs#L74
warning: field `0` is never read --> partiql-conformance-test-generator/src/schema.rs:74:20 | 74 | SyntaxFail(SyntaxFailAssertion), | ---------- ^^^^^^^^^^^^^^^^^^^ | | | field in this variant | help: consider changing the field to be of unit type to suppress this warning while preserving the field numbering, or remove the field | 74 | SyntaxFail(()), | ~~
field `0` is never read: partiql-conformance-test-generator/src/schema.rs#L73
warning: field `0` is never read --> partiql-conformance-test-generator/src/schema.rs:73:23 | 73 | SyntaxSuccess(SyntaxSuccessAssertion), | ------------- ^^^^^^^^^^^^^^^^^^^^^^ | | | field in this variant | = note: `#[warn(dead_code)]` on by default help: consider changing the field to be of unit type to suppress this warning while preserving the field numbering, or remove the field | 73 | SyntaxSuccess(()), | ~~
field `result` is never read: partiql-conformance-test-generator/src/schema.rs#L164
warning: field `result` is never read --> partiql-conformance-test-generator/src/schema.rs:164:13 | 163 | pub struct EvaluationFailAssertion { | ----------------------- field in this struct 164 | pub result: String, | ^^^^^^ | = note: `EvaluationFailAssertion` has derived impls for the traits `Clone` and `Debug`, but these are intentionally ignored during dead code analysis
field `result` is never read: partiql-conformance-test-generator/src/schema.rs#L157
warning: field `result` is never read --> partiql-conformance-test-generator/src/schema.rs:157:13 | 156 | pub struct EvaluationSuccessAssertion { | -------------------------- field in this struct 157 | pub result: String, | ^^^^^^ | = note: `EvaluationSuccessAssertion` has derived impls for the traits `Clone` and `Debug`, but these are intentionally ignored during dead code analysis
field `result` is never read: partiql-conformance-test-generator/src/schema.rs#L152
warning: field `result` is never read --> partiql-conformance-test-generator/src/schema.rs:152:13 | 151 | pub struct StaticAnalysisFailAssertion { | --------------------------- field in this struct 152 | pub result: String, | ^^^^^^ | = note: `StaticAnalysisFailAssertion` has derived impls for the traits `Clone` and `Debug`, but these are intentionally ignored during dead code analysis
field `result` is never read: partiql-conformance-test-generator/src/schema.rs#L147
warning: field `result` is never read --> partiql-conformance-test-generator/src/schema.rs:147:13 | 146 | pub struct SyntaxFailAssertion { | ------------------- field in this struct 147 | pub result: String, | ^^^^^^ | = note: `SyntaxFailAssertion` has derived impls for the traits `Clone` and `Debug`, but these are intentionally ignored during dead code analysis
field `result` is never read: partiql-conformance-test-generator/src/schema.rs#L142
warning: field `result` is never read --> partiql-conformance-test-generator/src/schema.rs:142:13 | 141 | pub struct SyntaxSuccessAssertion { | ---------------------- field in this struct 142 | pub result: String, | ^^^^^^ | = note: `SyntaxSuccessAssertion` has derived impls for the traits `Clone` and `Debug`, but these are intentionally ignored during dead code analysis
field `0` is never read: partiql-conformance-test-generator/src/schema.rs#L75
warning: field `0` is never read --> partiql-conformance-test-generator/src/schema.rs:75:28 | 75 | StaticAnalysisFail(StaticAnalysisFailAssertion), | ------------------ ^^^^^^^^^^^^^^^^^^^^^^^^^^^ | | | field in this variant | help: consider changing the field to be of unit type to suppress this warning while preserving the field numbering, or remove the field | 75 | StaticAnalysisFail(()), | ~~
field `0` is never read: partiql-conformance-test-generator/src/schema.rs#L74
warning: field `0` is never read --> partiql-conformance-test-generator/src/schema.rs:74:20 | 74 | SyntaxFail(SyntaxFailAssertion), | ---------- ^^^^^^^^^^^^^^^^^^^ | | | field in this variant | help: consider changing the field to be of unit type to suppress this warning while preserving the field numbering, or remove the field | 74 | SyntaxFail(()), | ~~
field `0` is never read: partiql-conformance-test-generator/src/schema.rs#L73
warning: field `0` is never read --> partiql-conformance-test-generator/src/schema.rs:73:23 | 73 | SyntaxSuccess(SyntaxSuccessAssertion), | ------------- ^^^^^^^^^^^^^^^^^^^^^^ | | | field in this variant | = note: `#[warn(dead_code)]` on by default help: consider changing the field to be of unit type to suppress this warning while preserving the field numbering, or remove the field | 73 | SyntaxSuccess(()), | ~~
Performance regression check
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.