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

proxy: improve test performance #8863

Merged
merged 5 commits into from
Aug 29, 2024
Merged

proxy: improve test performance #8863

merged 5 commits into from
Aug 29, 2024

Conversation

conradludgate
Copy link
Contributor

Some tests were very slow and some tests occasionally stalled. This PR improves some test performance and replaces the custom threadpool in order to fix the stalling of tests.

@conradludgate conradludgate marked this pull request as ready for review August 29, 2024 11:08
@conradludgate conradludgate requested a review from a team as a code owner August 29, 2024 11:08
Copy link
Contributor

@cloneable cloneable left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good

.config/nextest.toml Outdated Show resolved Hide resolved
Copy link

github-actions bot commented Aug 29, 2024

3801 tests run: 3695 passed, 0 failed, 106 skipped (full report)


Flaky tests (1)

Postgres 15

Code coverage* (full report)

  • functions: 32.5% (7409 of 22794 functions)
  • lines: 50.7% (60057 of 118567 lines)

* collected from Rust tests only


The comment gets automatically updated with the latest test results
b2e7844 at 2024-08-29T13:31:47.322Z :recycle:

@conradludgate conradludgate enabled auto-merge (squash) August 29, 2024 12:21
@conradludgate conradludgate merged commit 7ce49fe into main Aug 29, 2024
63 checks passed
@conradludgate conradludgate deleted the improve-proxy-tests branch August 29, 2024 13:20
conradludgate added a commit that referenced this pull request Aug 29, 2024
In #8863 I replaced the threadpool with tokio tasks, but there was a
behaviour I missed regarding cancellation. Adding the JoinHandle wrapper
that triggers abort on drop should fix this.

Another change, any panics that occur in password hashing will be
propagated through the resume_unwind functionality.
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.

2 participants