hello-stephen opened a new pull request, #70407:
URL: https://github.com/apache/doris/pull/70407

   ### Background
   
   The P0, CloudP0, and nonConcurrent pipelines select suites through their 
regression configuration files. A CI environment using rootless containers and 
temporary object-storage credentials is switching back to the unmodified 
framework built from the tested PR, removing pipeline-injected framework 
adapters.
   
   ### What problem does this PR solve?
   
   Issue Number: None
   Related PR: None
   PR Type: Build/CI/Chore
   
   Problem Summary:
   
   Temporarily exclude the specific suites with recorded framework-adapter 
failures in this migration environment: 59 P0, 9 CloudP0, and 2 nonConcurrent 
entries. The exclusions are opt-in through `DORIS_CI_PRISTINE_FRAMEWORK=true`; 
existing environments retain their current selection when the variable is 
absent or false. This change edits configuration only, without changing 
framework source, case assertions, or expected results.
   
   ### Details
   
   - **Affected:** The three pipeline configuration files. The list uses exact 
suite names, preserves existing exclusions, and adds no directory exclusions or 
wildcard patterns. Backup repository creation, temporary-credential/path 
routing, and local BE filesystem adapters account for the selected migration 
failures. These failures do not by themselves prove defects in the original 
community framework. Environment dependency failures, product assertions, 
unknown failures, and synthetic runner errors are excluded from this list. 
VaultP0 and External receive no new exclusions.
   - **Developer and release impact:** No default change. Migration CI opts in 
explicitly and reports its reduced coverage. Re-enable the suites after the 
relevant framework compatibility changes receive community review and 
validation; framework patches must not be injected by CI.
   - **License and third-party:** No new dependency or license change.
   - **Rollback:** Remove the opt-in environment variable to restore the 
original configuration selection, or revert this PR.
   
   ### Testing
   
   - Evaluated each added configuration block using Groovy 4.0.19 and Java 17 
with the opt-in variable both true and false (six checks).
   - Verified exact additions of 59 / 9 / 2 suite names with the variable true, 
preservation of an existing exclusion, and zero additions with the variable 
false.
   - Verified that the added names contain no wildcard patterns.
   - `git diff --check` passed.
   - A complete regression run using the new pristine-framework pipeline has 
not finished; the excluded cases are not reported as passing.
   
   ### Notes for Reviewers
   
   This is a temporary migration coverage reduction, not a framework fix. 
Review the opt-in boundary and the per-profile suite lists. Upstream framework 
compatibility fixes should be proposed separately with their own reproductions 
and tests.
   
   ### Release note
   
   None.
   
   ### Check List (For Author)
   
   - Behavior changed: Yes (opt-in migration CI suite selection only; see 
Details).
   - Does this need documentation: No (configuration comments document the 
opt-in switch).
   - Pre-submission status: Partially verified: configuration evaluation 
passed; complete migration regression validation remains outstanding.
   
   ### AI Disclosure
   
   - Tool: Codex, GPT-6.
   - Generated: Configuration additions and this PR description.
   - Human review: Pending.
   


-- 
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