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

feat: Reset pgrx environment post-tests #569

Merged
merged 4 commits into from
Nov 25, 2023
Merged

feat: Reset pgrx environment post-tests #569

merged 4 commits into from
Nov 25, 2023

Conversation

philippemnoel
Copy link
Collaborator

Ticket(s) Closed

  • Closes #N/A

What

From a recent PR, I set the tests to call their own cargo pgrx init to properly associate with system Postgres of the version they're testing against.

In order for the engineer to not need to re-call cargo pgrx init themselves after running the tests, we need to re-set it to the default project version after writing the tests. This does that.

Why

How

Tests

Copy link

vercel bot commented Nov 25, 2023

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Ignored Deployment
Name Status Preview Comments Updated (UTC)
paradedb ⬜️ Ignored (Inspect) Visit Preview Nov 25, 2023 11:34pm

Copy link

codecov bot commented Nov 25, 2023

Codecov Report

Merging #569 (cb331f6) into dev (ca29122) will not change coverage.
The diff coverage is n/a.

Additional details and impacted files
@@           Coverage Diff           @@
##              dev     #569   +/-   ##
=======================================
  Coverage   60.14%   60.14%           
=======================================
  Files          42       42           
  Lines        3475     3475           
=======================================
  Hits         2090     2090           
  Misses       1385     1385           

@philippemnoel philippemnoel merged commit 83fd5d5 into dev Nov 25, 2023
25 checks passed
@philippemnoel philippemnoel deleted the phil/reset-pgrx branch November 25, 2023 23:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant