featzhang commented on PR #28048:
URL: https://github.com/apache/flink/pull/28048#issuecomment-4341471151

   ## CI Failure Root-Cause Analysis (Build 
[#74590](https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=74590))
   
   Quick summary: all 11 failing tasks trace back to **Azure infrastructure 
issues on the `release-1.15` branch, not to this change**. Evidence below.
   
   ### 1. Primary cause — Azure agent pool image label no longer exists for 
`release-1.15`
   
   Three independent jobs fail at the agent-provisioning stage with the 
identical infrastructure error:
   
   | Job | Error message |
   |---|---|
   | `e2e_1_ci` | `No image label found to route agent pool Azure Pipelines.` |
   | `e2e_2_ci` | `No image label found to route agent pool Azure Pipelines.` |
   | `docs_404_check` | `No image label found to route agent pool Azure 
Pipelines.` |
   
   These jobs never start executing — they die before `git clone`. The Azure 
Pipelines agent pool used by the `release-1.15` pipeline definition no longer 
advertises the image label those jobs request. This is a pipeline-configuration 
/ agent-pool issue on the infra side, not something a PR change can fix.
   
   ### 2. Secondary cause — `Test - connectors` flaky + cascade
   
   - `Test - connectors` → `Bash exited with code '1'` (no Java stack trace 
surfaced in the task log — the failure is in the outer bash wrapper, consistent 
with the pre-existing flakiness seen on other recent `release-1.15` PRs).
   - `PublishTestResults` → `No test result files matching '**/TEST-*.xml' were 
found.` — this is a **direct cascade** of the above: the test step exited 
before Surefire produced the XML reports.
   - `test_ci connectors` (Job) / `test_ci` (Phase) / `CI build (custom 
builders)` (Stage) — all have empty messages, they are simply the Stage/Phase 
wrappers propagating the child task's failure.
   
   ### 3. Relationship to this PR's changes
   
   This PR only touches 6 files under 
`flink-table/flink-table-runtime/src/{main,test}/java/org/apache/flink/{formats,table/formats}/raw/`:
   
   - `RawFormatDeserializationSchema.java`, 
`RawFormatSerializationSchema.java`, `RawFormatFactory.java`, 
`RawFormatOptions.java`
   - `RawFormatFactoryTest.java`, `RawFormatLineDelimiterTest.java` (new)
   
   **Zero overlap** with:
   - the e2e test suites (`e2e_1_ci`, `e2e_2_ci`),
   - the connectors module (`Test - connectors`),
   - the docs pipeline (`docs_404_check`).
   
   The only module that actually exercises this change is 
`flink-table-runtime`, which was not among the reported failures. I also re-ran 
the targeted unit tests locally:
   
   ```
   mvn test -pl flink-table/flink-table-runtime -Dtest='RawFormat*'
   → Tests run: 51, Failures: 0, Errors: 0, Skipped: 0
   ```
   (11 new `RawFormatLineDelimiterTest` + 7 `RawFormatFactoryTest` + 33 
pre-existing SerDe tests.)
   
   ### 4. Context: `release-1.15` is EOL
   
   As I noted in the PR description, `release-1.15` is past its community 
maintenance window. The Azure agent-pool image label removal and the 
connectors-test flakiness are both manifestations of the EOL infrastructure no 
longer being actively maintained, and re-running CI (I already pushed an empty 
commit `d5efa5f` to retrigger — same failure pattern) will not produce a green 
build on this branch under the current configuration.
   
   ### Request
   
   Given (a) the change is identical to the already-merged master PR #27897, 
(b) the failures are infrastructure-only and unrelated to the diff, and (c) 
local tests pass cleanly — would a committer with `release-1.15` merge access 
be willing to merge this via a no-CI-required path? Happy to add the two 
`docs/**/raw.md` doc files from #27897 as well if that helps.
   
   cc @spuru9 (already approved), and anyone still active on `release-1.15` 
maintenance.


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

Reply via email to