SEPURI-SAI-KRISHNA commented on issue #12968:
URL: https://github.com/apache/seatunnel/issues/12968#issuecomment-6434279612
@SEZ9 the rerun has finished, and it settles both of your asks.
**1. `AmazonDocumentDBIT.testProjection` did not fail again, so there is no
log link to post.**
The lane that failed before is `updated-modules-integration-test-part-3 (11,
ubuntu-latest)`. On the rerun it passed:
```
Tests run: 21, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 652.731 s
- in org.apache.seatunnel.e2e.connector.amazondocumentdb.AmazonDocumentDBIT
```
Those 21 are 3 methods across 7 engine containers, and the Spark 3.3
container is among the variants that ran:
| method | runs | failures |
| --- | --- | --- |
| `testBasicRead` | 7 | 0 |
| `testProjection` | 7 | 0 |
| `testQueryFilter` | 7 | 0 |
So the earlier `row num: 0` did not reproduce. I would rather call that
unreproduced than call it diagnosed: I have no root cause for the first
failure, only the evidence that it does not recur and that it cannot plausibly
come from this change. That reasoning is unchanged from when I reported it,
namely that the connector has no arrow references in its main sources and the
job only ran at all because `connector-common` is an upstream module of every
connector, which widens the updated-modules set.
**2. Build is green on the exact head you named.**
| | |
| --- | --- |
| head | `a66150a38` |
| Build | SUCCESS |
| completed | 2026-10-26T07:53:16Z |
The green belongs to `a66150a38` itself rather than to an earlier commit, so
it is the head you said you would take a final look at. I also re-checked the
merge state after `dev` moved to `c875a87bd` today: still `MERGEABLE`, no
conflict.
Nothing on the change itself has moved since your last review. The three
`ArrowToSeatunnelRowReaderNullCellTest` cases, the EN and ZH
`incompatible-changes.md` entries for the MAP behaviour change, and the
untouched `// todo check map` in `ArrowToSeatunnelRowReaderTest` are all
exactly as described.
From my side the only remaining gate on #12969 is the write-access review.
--
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]