Intermittent test failures on CI [DBZ-3230]
- Dominant language
- HTML
- Stars
- 6
- Forks
- 8
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 1
Description
Migrated from [DBZ-3230](https://issues.redhat.com/browse/DBZ-3230)
{code}
Error: customSnapshotterSkipsTablesOnRestartWithConcurrentTx(io.debezium.connector.postgresql.PostgresConnectorIT) Time elapsed: 154.642 s <<< ERROR!
org.awaitility.core.ConditionTimeoutException: Condition with alias 'Streaming was not started on time' didn't complete within 2 minutes 30 seconds because condition with io.debezium.connector.postgresql.PostgresConnectorIT was not fulfilled.
at io.debezium.connector.postgresql.PostgresConnectorIT.customSnapshotterSkipsTablesOnRestartWithConcurrentTx(PostgresConnectorIT.java:1769)
Caused by: java.util.concurrent.TimeoutException
at io.debezium.connector.postgresql.PostgresConnectorIT.customSnapshotterSkipsTablesOnRestartWithConcurrentTx(PostgresConnectorIT.java:1769)
{code}
Ref : [here|https://github.com/debezium/debezium/runs/1952862772?check_suite_focus=true]
Contributor guide
Research direction
Start with the linked CI run and io.debezium.connector.postgresql.PostgresConnectorIT.customSnapshotterSkipsTablesOnRestartWithConcurrentTx at PostgresConnectorIT.java:1769. Trace the Awaitility condition named “Streaming was not started on time” and reproduce the restart with a concurrent transaction. Done means the test completes reliably without the reported timeout.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, postgresql
- Domain
- ci-cd, databases, testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100