Source: sqlalchemy
Severity: important
X-Debbugs-Cc: [email protected]
Hello,
while checking how #997484 was possible, thinking that it should have been
caught while running tests at build time, i noticed that.. tests are not run at
build time.
Maybe there's a reason for this, but i could not find any info the in the
changelog regading ever enabling/disabling tests; but i just installed pytest,
run it and got:
```
Traceback (most recent call last):
File
"/build/sqlalchemy-1.4.23+ds1/test/../lib/sqlalchemy/testing/plugin/pytestplugin.py",
line 772, in decorate
asyncio._run_coroutine_function(fn, *args, **kwargs)
File
"/build/sqlalchemy-1.4.23+ds1/test/../lib/sqlalchemy/testing/asyncio.py", line
33, in _run_coroutine_function
return _util_async_run_coroutine_function(fn, *args, **kwargs)
File
"/build/sqlalchemy-1.4.23+ds1/test/../lib/sqlalchemy/util/concurrency.py", line
59, in _util_async_run_coroutine_function
_not_implemented()
File
"/build/sqlalchemy-1.4.23+ds1/test/../lib/sqlalchemy/util/concurrency.py", line
36, in _not_implemented
raise ValueError(
ValueError: the greenlet library is required to use this function.
```
and other variation of the same error, and that's the only cause of errors in
the tests (along with a lot of skipped tests, likely due to missing dependencies
on db backends, tests setup, etc etc).
I think the first step is to setup tests at build time, and given the importance
of this package in debian, also autopkgtests should be enabled. I set the
severity to important to reflect that.
Regards,
Sandro
-- System Information:
Debian Release: 11.0
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.10.0-8-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
