test_sqlite_filelock_bucket is unstable.

[Enimalojd]

Hello! :)

When building your project for the ALT family repositories in an isolated environment, test_sqlite_filelock_bucket may hang forever without giving any errors.

I would also like to draw your attention to the fact that in Fedora and Archlinux your project is being built without tests. Fedora explains this by the absence of some packages that are either outdated in their repository or completely missing, but I would also like to add to this that your project requires redis and postgres to be raised in an isolated environment in order to run all tests during build, which is not a good practice.
https://src.fedoraproject.org/rpms/python-pyrate-limiter/blob/rawhide/f/python-pyrate-limiter.spec
https://gitlab.archlinux.org/archlinux/packaging/packages/python-pyrate-limiter/-/blob/main/PKGBUILD?ref_type=heads

TY. :)

[paultiq]

ty!

I'm not really familiar with these repos or builds... is there a log you can point at?

Is there any sense of what Python version these tests are running on?

[Enimalojd]

I'm attaching the build log. ALT Sisyphus, Python 3.13
Run tests with command python3 -m pytest -vra

build.log

diff --git a/tests/conftest.py b/tests/conftest.py
index 8023a8f..38f6742 100644
--- a/tests/conftest.py
+++ b/tests/conftest.py
@@ -118,10 +118,7 @@ async def create_postgres_bucket(rates: List[Rate]):
 @pytest.fixture(
     params=[
         create_in_memory_bucket,
-        create_redis_bucket,
         create_sqlite_bucket,
-        create_async_redis_bucket,
-        create_postgres_bucket,
         create_filelocksqlite_bucket,
         pytest.param(create_mp_bucket, marks=pytest.mark.mpbucket)
     ]

The only changes I've made are these. Since there is no Internet inside hasher (https://en.altlinux.org/Hasher) and it is not advisable to use any third-party services like redis or postgres for the purity of the build.
As you can see, the test not only fails, but also does not crash with any errors (for example, time timeouts). I waited for more than two hours.

Thank you so much for your interest in the question!

[paultiq]

If SQLite-filelock is failing, it may be an issue with the filelock on this platform. We could add a 'is filelock stable' test that's separate from the SQLite test platform, perhaps.

Also, I see that this uses 3.13.0. I didn't look at change log, but the current patch level for 3.13 is 3.13.9. I don't know if any patch is related, but building with current patch level is worth considering.

Is there a docker image to run this build?