oracleloyall opened a new pull request, #1899:
URL: https://github.com/apache/cloudberry/pull/1899

   Several regression files carry large blocks of cases whose coverage is 
already provided by other cases in the same file, and fixtures sized far beyond 
what the assertions actually need.  Removing them shortens the test run without 
dropping any distinct behaviour under test.
   
   src/test/regress:
   
     qp_olap_window     Every functional label (window function x frame
                        clause x partition clause) was repeated 16 times
                        with only the projected column list permuted, which
                        produces the same plan and the same result shape.
                        Keep four variants per label: 2977 -> 1104
                        statements, 24035 -> 8875 lines.
   
     qp_olap_windowerr  The same error paths (division by zero, invalid
                        preceding/following size, negative frame offset)
                        are repeated once per aggregate.  Keep one
                        aggregate per error class: 440 -> 213 statements.
                        All 24 distinct ERROR messages are still produced.
   
     qp_dropped_cols    The decimal axis duplicates the numeric axis
                        exactly, decimal being an alias of numeric, so drop
                        it: 4000 -> 3426 statements.
   
     qp_gist_indexes2   The compression axis does not interact with the
                        GiST index behaviour under test; drop it:
                        522 -> 320 statements.
   
     cbdb_parallel      Shrink the parallel bitmap heap scan fixtures from
                        10,000,000 rows to 1,000,000 and 2,000,000, and
                        from 5,000,000 to 1,000,000.  The plan shapes being
                        asserted do not depend on the row counts.
   
   src/test/isolation2:
   
     uao/fast_analyze   Drop three doubling steps from the data pyramid,
                        4,608,000 -> 1,152,000 rows.  The test only checks
                        that the sample scan touches a bounded number of
                        blocks, which the smaller table already exceeds.
   
   contrib/pax_storage/src/test:
   
     The PAX suites carry verbatim copies of 103 test files that do not
     exercise PAX storage at all: the gp_interconnect_* family (11 files),
     qp_* query-processing cases (20), FTS and recovery cases (4), and
     further storage-independent cases.  All of them already run in the
     main suites.  Remove the files together with their schedule entries:
   
       regress/greenplum_schedule      397 -> 307 tests
       regress/parallel_schedule       183 -> 175 tests
       isolation2/isolation2_schedule  146 -> 141 tests
   
   No schedule is left with a dangling reference, no remaining test depends on 
an object created by a removed one, and no test file becomes unreferenced by 
the removal.
   
   Verified on a three-segment demo cluster built with --enable-pax by running 
each suite before and after the change in both optimizer modes with 
default_table_access_method=pax: the change introduces no new failures, and the 
PAX regress suite drops from 575 to 477 executed tests.
   
   Author: zhaoxi <[email protected]>
   
   <!-- Thank you for your contribution to Apache Cloudberry (Incubating)! -->
   
   Fixes #ISSUE_Number
   
   ### What does this PR do?
   <!-- Brief overview of the changes, including any major features or fixes -->
   
   ### Type of Change
   - [ ] Bug fix (non-breaking change)
   - [ ] New feature (non-breaking change)
   - [ ] Breaking change (fix or feature with breaking changes)
   - [ ] Documentation update
   
   ### Breaking Changes
   <!-- Remove if not applicable. If yes, explain impact and migration path -->
   
   ### Test Plan
   <!-- How did you test these changes? -->
   - [ ] Unit tests added/updated
   - [ ] Integration tests added/updated
   - [ ] Passed `make installcheck`
   - [ ] Passed `make -C src/test installcheck-cbdb-parallel`
   
   ### Impact
   <!-- Remove sections that don't apply -->
   **Performance:**
   <!-- Any performance implications? -->
   
   **User-facing changes:**
   <!-- Any changes visible to users? -->
   
   **Dependencies:**
   <!-- New dependencies or version changes? -->
   
   ### Checklist
   - [ ] Followed [contribution 
guide](https://cloudberry.apache.org/contribute/code)
   - [ ] Added/updated documentation
   - [ ] Reviewed code for security implications
   - [ ] This PR contains AI-assisted code generation
   - [ ] Requested review from [cloudberry 
committers](https://github.com/orgs/apache/teams/cloudberry-committers)
   
   ### Additional Context
   <!-- Any other information that would help reviewers? Remove if none -->
   
   ### CI Skip Instructions
   <!--
   To skip CI builds, add the appropriate CI skip identifier to your PR title.
   The identifier must:
   - Be in square brackets []
   - Include the word "ci" and either "skip" or "no"
   - Only use for documentation-only changes or when absolutely necessary
   -->
   
   ---
   <!-- Join our community:
   - Mailing list: 
[[email protected]](https://lists.apache.org/[email protected])
 (subscribe: [email protected])
   - Discussions: https://github.com/apache/cloudberry/discussions -->
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to