- Notifications
You must be signed in to change notification settings - Fork67
PostgreSQL-13 compatibility#220
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
codecovbot commentedOct 23, 2020 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
Codecov Report
@@ Coverage Diff @@## master #220 +/- ##==========================================- Coverage 91.87% 91.36% -0.51%========================================== Files 40 43 +3 Lines 7052 7181 +129 ==========================================+ Hits 6479 6561 +82- Misses 573 620 +47
Continue to review full report at Codecov.
|
d020b61
toa694344
CompareAlso try to log tail of PG logs on CI in a brave hope of catching troublesthere. Currently travis job on 10 rarely fails at test_concurrent_updates, butwe've failed to reproduce the issue locally. Note that test_concurrent_updatesactually doesn't perform anything useful as testgres nodes aren't pickable dueto weird logging implemented in separate thread, but nobody cared to checkapply_async result so this has went unnoticed for a long time.
Reworded commit message and merged. |
No description provided.