gnodet commented on PR #25417:
URL: https://github.com/apache/camel/pull/25417#issuecomment-5238103567

   ## ❌ Local IT results for `677672a10f6e`
   
   Behavioral change detected in docling v1.30.0 — page furniture (footers) are 
now included in body export.
   
   **Test-infra module**: `camel-test-infra-docling`
   **Components tested**: `camel-docling`
   
   | Component | Tests | Passed | Failed | Errors | Skipped | Status |
   |-----------|-------|--------|--------|--------|---------|--------|
   | `camel-docling` | 9 | 6 | 1 | 2 | 0 | ❌ behavioral change + timeouts |
   
   ### Behavioral change (requires human review)
   
   **`OcrExtractionIT.testOcrWithMultipleTextBlocks`** — **FAILS** because 
docling v1.30.0 now includes page furniture (footer text) in the body export.
   
   The test at line 182-190 was **explicitly designed** as a detection 
assertion for this exact change:
   ```java
   // This assertion documents and pins that behavior; it will start failing if 
a
   // future docling release includes page furniture in the body export, 
prompting us to revisit the limitation.
   boolean foundFooter = resultLower.contains("footer");
   assertFalse(foundFooter, "Footer text is page furniture and is excluded from 
the docling body export...");
   ```
   
   The result now contains: _"This is the first paragraph with multiple lines 
of text / Second paragraph starts here containing more information / **Footer: 
Apache Camel Docling Component**"_ — the footer IS present.
   
   **Impact**: This is a user-visible behavioral change. Previously, docling's 
body export (Markdown/text/HTML) excluded the FURNITURE content layer 
(headers/footers). Version v1.30.0 includes it. Camel users processing scanned 
documents will now see header/footer text in their output.
   
   **Recommended actions**:
   1. Update the test assertion to expect the new behavior (footer text present)
   2. Update documentation in `docling-component.adoc` regarding the "OCR and 
page headers/footers" note
   3. Consider whether this requires an upgrade guide entry
   
   ### Resource constraint timeouts (not container-related)
   
   - `OcrExtractionIT.testOcrJsonConversionFromImage` — `HttpTimeoutException: 
request timed out` (121.5s)
   - `ExtractStructuredDataIT.extractStructuredDataFromInvoice` — 
`HttpTimeoutException: request timed out` (122.7s)
   - Fork timeout prevented `ChunkingIT` from running
   
   These timeouts are due to the heavy AI model container under resource 
constraints, not behavioral changes.
   
   > _Local integration tests run by ForgeBot on behalf of @gnodet_
   > _Tests run without `-Dci.env.name` to include ITs disabled on GitHub 
Actions CI_


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