Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update README.md #1743

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update README.md #1743

wants to merge 1 commit into from

Conversation

mrugeshgharat
Copy link

@mrugeshgharat mrugeshgharat commented Feb 26, 2025

Updated the partiql-website-plk link to point to https://partiql.org/plk/1.0/

Relevant Issues

  • [Closes/Related To] Issue #XXX

Description

  • This change is to fix the PLK website link in the readme document.

Other Information

  • Updated Unreleased Section in CHANGELOG: [NO]

  • This is a minor change to fix the PLK website link.

  • Any backward-incompatible changes? [NO]

  • Any new external dependencies? [NO]

  • Do your changes comply with the Contributing Guidelines
    and Code Style Guidelines? [YES]

License Information

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Updated the partiql-website-plk link to point to https://partiql.org/plk/1.0/
Copy link

CROSS-ENGINE-REPORT ❌

BASE (LEGACY-V0.14.8) TARGET (EVAL-8D4F628) +/-
% Passing 89.67% 94.96% 5.29% ✅
Passing 5287 5618 331 ✅
Failing 609 74 -535 ✅
Ignored 0 224 224 🔶
Total Tests 5896 5916 20 ✅

Testing Details

  • Base Commit: v0.14.8
  • Base Engine: LEGACY
  • Target Commit: 8d4f628
  • Target Engine: EVAL

Result Details

  • ❌ REGRESSION DETECTED. See Now Failing/Ignored Tests. ❌
  • Passing in both: 2622
  • Failing in both: 18
  • Ignored in both: 0
  • PASSING in BASE but now FAILING in TARGET: 16
  • PASSING in BASE but now IGNORED in TARGET: 102
  • FAILING in BASE but now PASSING in TARGET: 179
  • IGNORED in BASE but now PASSING in TARGET: 0

Now FAILING Tests ❌

The complete list can be found in GitHub CI summary, either from Step Summary or in the Artifact.

Now IGNORED Tests ❌

The complete list can be found in GitHub CI summary, either from Step Summary or in the Artifact.

Now Passing Tests

179 test(s) were previously failing in BASE (LEGACY-V0.14.8) but now pass in TARGET (EVAL-8D4F628). Before merging, confirm they are intended to pass.

The complete list can be found in GitHub CI summary, either from Step Summary or in the Artifact.

CROSS-COMMIT-REPORT ❌

BASE (EVAL-742E150) TARGET (EVAL-8D4F628) +/-
% Passing 94.96% 94.96% 0.00% ✅
Passing 5618 5618 0 ✅
Failing 74 74 0 ✅
Ignored 224 224 0 ✅
Total Tests 5916 5916 0 ✅

Testing Details

  • Base Commit: 742e150
  • Base Engine: EVAL
  • Target Commit: 8d4f628
  • Target Engine: EVAL

Result Details

  • ❌ REGRESSION DETECTED. See Now Failing/Ignored Tests. ❌
  • Passing in both: 5618
  • Failing in both: 74
  • Ignored in both: 224
  • PASSING in BASE but now FAILING in TARGET: 8
  • PASSING in BASE but now IGNORED in TARGET: 0
  • FAILING in BASE but now PASSING in TARGET: 8
  • IGNORED in BASE but now PASSING in TARGET: 0

Now FAILING Tests ❌

The following 8 test(s) were previously PASSING in BASE but are now FAILING in TARGET:

Click here to see
  1. group by with where, compileOption: PERMISSIVE
  2. group by with where, compileOption: STRICT
  3. group by with group as and where, compileOption: PERMISSIVE
  4. group by with group as and where, compileOption: STRICT
  5. structs should be ordered by data types (DESC) (nulls first as default for desc), compileOption: PERMISSIVE
  6. structs should be ordered by data types (DESC) (nulls first as default for desc), compileOption: STRICT
  7. repeated field on struct is ambiguous{identifier:"REPEATED",cn:9,bn:"REPEATED"}, compileOption: STRICT
  8. repeated field on struct is ambiguous{identifier:" "repeated" ",cn:10,bn:"repeated"}, compileOption: STRICT

Now Passing Tests

The following 8 test(s) were previously FAILING in BASE but are now PASSING in TARGET. Before merging, confirm they are intended to pass:

Click here to see
  1. repeated field on struct is ambiguous{identifier:"REPEATED",cn:9,bn:"REPEATED"}, compileOption: STRICT
  2. repeated field on struct is ambiguous{identifier:" "repeated" ",cn:10,bn:"repeated"}, compileOption: STRICT
  3. group by with where, compileOption: PERMISSIVE
  4. group by with where, compileOption: STRICT
  5. group by with group as and where, compileOption: PERMISSIVE
  6. group by with group as and where, compileOption: STRICT
  7. structs should be ordered by data types (DESC) (nulls first as default for desc), compileOption: PERMISSIVE
  8. structs should be ordered by data types (DESC) (nulls first as default for desc), compileOption: STRICT

@jpschorr
Copy link
Contributor

Rendered

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants