Add Logging to Diagnose Flaky CI PostgreSQL Integration Test #1308
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I observed flakiness in the CI PostgreSQL integration tests. Here's an example of a failure: https://github.com/lightninglabs/taproot-assets/actions/runs/12827900128/attempts/1?pr=1307
The issue occurred around commit ffef906.
This might be happening because proofs are being transferred manually before the tapd state machine has a chance to process them. Alternatively, it could be due to tapd returning an error in the event stream with an out-of-order send state, realizing it cannot transfer the proofs that haven't yet been manually transferred.
To address this, I've added additional logging to help diagnose the issue if the flakiness occurs again.
Full log file: 4_run itest.txt