DanielLeens commented on PR #12323:
URL: https://github.com/apache/seatunnel/pull/12323#issuecomment-5678773946
One more thing worth flagging now that CI has finished: the `Build` check on
this PR (fork run job `rocketmq-connector-it (11, ubuntu-latest)`) came back
red with 7 errors, all the same signature:
```
org.awaitility.core.ConditionTimeoutException: ... Consume offset should be
visible for MessageQueue [topic=test_topic, ...] ==> expected: not <null>
within 1 minutes.
at RocketMqIT.waitConsumedOffsetsSynced(RocketMqIT.java:585)
at RocketMqIT.getRocketMqConsumerData(RocketMqIT.java:566)
at RocketMqIT.testSinkRocketMq(RocketMqIT.java:199)
```
This is not caused by this PR — `testSinkRocketMq` and
`waitConsumedOffsetsSynced` are untouched by this diff, and the failure is on
the consumer-offset-commit-visibility side of a *sink* test (`test_topic`), not
the topic-route warm-up this PR addresses. It's also already a known,
previously-documented flake: the existing comment right above the
`Awaitility.await()` call in `waitConsumedOffsetsSynced` (pre-dating this PR)
already records a prior occurrence of this exact same assertion timing out
under CI load on a different JDK leg of a different run. So this looks like the
same pre-existing broker-side offset-visibility flake recurring, not a new
regression from this change.
No action needed on your side for this specific failure — a rerun of the
`Build` check should be enough. I don't have permission to trigger a rerun on
your fork myself, so if you get a chance, please retrigger the failed job (or
push an empty commit / use the "Re-run failed jobs" button if GitHub exposes it
to you on your fork).
--
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]
