Skip to content
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Parallel tests fail on upgrades #226

Closed
Ngalstyan4 opened this issue Nov 18, 2023 · 0 comments · Fixed by #246
Closed

Parallel tests fail on upgrades #226

Ngalstyan4 opened this issue Nov 18, 2023 · 0 comments · Fixed by #246
Assignees
Labels
bug Something isn't working

Comments

@Ngalstyan4
Copy link
Contributor

Ngalstyan4 commented Nov 18, 2023

Parallel tests (inserts, in particular) often fail with an error message when running upgrade script from 0.0.4 to 0.05:

+ERROR:  tuple concurrently updated

Note that in upgrade process, begin.sql runs with the old extension version, while the rest of the tests run with the newer version of the extension.

See an example failure here: https://github.com/lanterndata/lantern/actions/runs/6910547384/job/18803850282?pr=223

I have not disabled these update tests but have just made sure they do not result in the failure of the whole suite. So, to debug this, you can make a regular PR and see the failure logs under "Run update tests linux" subsection of the CI log

@Ngalstyan4 Ngalstyan4 added the bug Something isn't working label Nov 18, 2023
Ngalstyan4 added a commit that referenced this issue Nov 18, 2023
Fix wront return code check

Add index validation functions to update script

Fix update test runner logic

We used to run new tests on the old DB.
This need not always succeed as new tests may use/test functionality
from the newer version of the DB.
In the new approach, we only run tests *after* upgrade script has
been run.

Make common.sql idempotent

Suppress common output and add update comments

Rename main -> from_tags[-1] in update script

Do not fail on parallel test failure during update (tracked by #226)
Ngalstyan4 added a commit that referenced this issue Nov 18, 2023
Fix wront return code check

Add index validation functions to update script

Fix update test runner logic

We used to run new tests on the old DB.
This need not always succeed as new tests may use/test functionality
from the newer version of the DB.
In the new approach, we only run tests *after* upgrade script has
been run.

Make common.sql idempotent

Suppress common output and add update comments

Rename main -> from_tags[-1] in update script

Do not fail on parallel test failure during update (tracked by #226)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants