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

Fix: nextest cleanup race condition #3334

Merged
merged 21 commits into from
Jan 24, 2025

Conversation

bonega
Copy link
Contributor

@bonega bonega commented Jul 7, 2024

fixes #2123 #[sqlx::test] should play nicely with nextest

Nextest provides a NEXTEST_RUN_ID that we can use to clear up tests belonging to the same cargo invocation.

See for a more general fix for cargo test runners.

Currently I haven't implemented support for mysql and sqlite, I'm looking for feedback before going ahead and doing that.

@bonega bonega changed the title Work around nextest cleanup race condition Fix: nextest cleanup race condition Jul 8, 2024
Copy link
Collaborator

@abonander abonander left a comment

Choose a reason for hiding this comment

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

Looks decent so far. Requesting changes so when you hit "request review" I know to check back.

@abonander
Copy link
Collaborator

abonander commented Jul 19, 2024

@bonega another thought is, instead of generating an arbitrary database name, we could generate one based on the path of the test function that's running. If the database name is always the same, then there's no real extra cleanup step necessary besides dropping and recreating the database before running the test and dropping it afterward. And it would make it a lot easier to find and inspect the database in question.

I would honestly make it always clean up the test database afterward unless an environment variable is set; the existing behavior seems to just confuse and annoy people more than anything. Bikeshedding: SQLX_TEST_KEEP_DB?

Do you know of any test runners that execute the same function multiple times concurrently? I think we could even handle that by holding a lock on the row in the test-databases table as a mutex. Arguably though, that table wouldn't even need to exist.

I think the main reason I didn't just do this originally was because I didn't want to have to think of a way to convert a path to a database name. However, as it turns out, MySQL and Postgres both allow (quoted) database names to contain any character besides NUL (\0) so we don't really have to come up with any special mapping scheme; we could just use the fully qualified path of the test function itself.

The biggest potential issue is that both databases have a length limit of 64 and 63 characters, respectively, so we'd have to either abbreviate or just truncate. I guess truncating makes the most sense. 63 characters is quite a lot for a path, it's unlikely to collide in most situations. If there is a collision, the mutual exclusion would just make the tests execute serially. And we could always make the attribute take an argument to override the database name.

@bonega
Copy link
Contributor Author

bonega commented Jul 22, 2024

Hey, just giving a heads-up that I am super busy with moving apartment, will take a closer look on this in a couple of days.

@abonander
Copy link
Collaborator

@bonega do you have time to look at my last comment?

@bonega
Copy link
Contributor Author

bonega commented Jul 30, 2024

@bonega do you have time to look at my last comment?

It is starting to wind down now, think I will have time today or tomorrow

@bonega
Copy link
Contributor Author

bonega commented Aug 1, 2024

@abonander
I think it seems to be a generally good idea.
Though I worry a bit about the truncating/locking. I have seen some very long test names before.

I will do some prototyping and see if it seems workable.

@abonander
Copy link
Collaborator

To get the module path you'll probably need to make #[sqlx::test] emit a recursive invocation of itself with module_path!() in its arguments. It's very fortunate that arguments to attributes are expanded eagerly now.

@bonega
Copy link
Contributor Author

bonega commented Aug 11, 2024

Hey, Sorry for being unresponsive.

I have checked around a little.
The test path can easily get long since it also includes the modules.
Also I don't want to impose naming requirements on the end-users.

By doing a truncate and lock I fear that we might regress the performance for some of the current users.

@abonander
Copy link
Collaborator

@bonega we could instead hash the path. A SHA-256 hash is incredibly unlikely to collide and can be encoded in 64 hex characters, so in Base64 (with dash and underscore) would be more like... 40?

I think deterministic naming is the right answer here, because then each test function can be wholly responsible for its own database and doesn't need any sort of memoization.

@bonega
Copy link
Contributor Author

bonega commented Sep 1, 2024

@abonander Hey, I am getting back into shape now.

Is this in the direction of what you wanted?
Will do some more refactoring and fixing up if it looks alright.

@bonega bonega force-pushed the nextest-race-condition branch from b27a056 to ba296be Compare September 2, 2024 09:12
Copy link
Collaborator

@abonander abonander left a comment

Choose a reason for hiding this comment

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

Some nits, otherwise it looks all right.

Cargo.toml Outdated Show resolved Hide resolved
sqlx-core/src/testing/mod.rs Outdated Show resolved Hide resolved
Ok(Some(num_deleted))
})
}

Copy link
Collaborator

Choose a reason for hiding this comment

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

Reminder to check this trait implementation for proper quoting of the database name. It doesn't look like it does it.

Copy link
Collaborator

Choose a reason for hiding this comment

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

@bonega don't forget this. Even with URL_SAFE the database name still needs to be quoted because it may contain dashes.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I checked and it seems to work.

A test in examples/postgres/axum-social-with-tests has the test_path: comment::test_create_comment
Which becomes the database name of _sqlx_test_hsAQWz-87IRR7sjnVDeMcHtoDLU3QyT6yWizSbWKFvNwoBt6Q60I

It is deleted correctly even though it contains dashes.

I see now that you're referencing the mysql implementation which I haven't started yet.
I will try and do it and the sqlite today.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Just to update that I am fighting with running the tests on (both my branch and main)

@bonega
Copy link
Contributor Author

bonega commented Sep 15, 2024

@abonander I still can't run the tests locally but I see that this is passing in CI.
Mysql is finished and from what I can see sqlite already does a database per test path.

@bonega bonega requested a review from abonander September 15, 2024 19:42
Copy link
Collaborator

@abonander abonander left a comment

Choose a reason for hiding this comment

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

One blocking change ({db_name:?}), one non-blocking (cleanup_test_dbs()).

Also, what failure are you getting locally? I can't help without any details.

sqlx-mysql/src/testing/mod.rs Outdated Show resolved Hide resolved
sqlx-core/src/testing/mod.rs Outdated Show resolved Hide resolved
@bonega bonega requested a review from abonander September 16, 2024 10:53
@bonega bonega requested a review from abonander September 20, 2024 10:40
@bonega
Copy link
Contributor Author

bonega commented Oct 27, 2024

@s373r Thank you.
I imported what I think was the gist of your changes.

Copy link

@s373r s373r left a comment

Choose a reason for hiding this comment

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

Added comments

sqlx-core/src/testing/mod.rs Show resolved Hide resolved
sqlx-sqlite/src/testing/mod.rs Outdated Show resolved Hide resolved
Copy link

@s373r s373r left a comment

Choose a reason for hiding this comment

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

LGTM

@s373r
Copy link

s373r commented Nov 12, 2024

@abonander , could you please merge the PR?

@DerPlayer2001
Copy link

@abonander how could we help getting this PR merged?

@ddxgod
Copy link

ddxgod commented Jan 14, 2025

@abonander bump on this; would be great to get this merged, thanks!

@jonwalch

This comment was marked as spam.

@abonander abonander merged commit a83395a into launchbadge:main Jan 24, 2025
81 checks passed
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.

#[sqlx::test] should play nicely with nextest
6 participants