mirror of
https://github.com/neondatabase/neon.git
synced 2025-12-26 23:59:58 +00:00
The CI times out after 10 minutes of no output. It's annoying if a test hangs and is killed by the CI timeout, because you don't get information about which test was running. Try to avoid that, by adding a slightly smaller timeout in pytest itself. You can override it on a per-test basis if needed, but let's try to keep our tests shorter than that. For the Postgres regression tests, use a longer 30 minute timeout. They're not really a single test, but many tests wrapped in a single pytest test. It's OK for them to run longer in aggregate, each Postgres test is still fairly short.
37 lines
804 B
TOML
37 lines
804 B
TOML
[tool.poetry]
|
|
name = "zenith"
|
|
version = "0.1.0"
|
|
description = ""
|
|
authors = []
|
|
|
|
[tool.poetry.dependencies]
|
|
python = "^3.9"
|
|
pytest = "^6.2.5"
|
|
psycopg2-binary = "^2.9.1"
|
|
typing-extensions = "^3.10.0"
|
|
PyJWT = {version = "^2.1.0", extras = ["crypto"]}
|
|
requests = "^2.26.0"
|
|
pytest-xdist = "^2.3.0"
|
|
asyncpg = "^0.24.0"
|
|
aiopg = "^1.3.1"
|
|
cached-property = "^1.5.2"
|
|
Jinja2 = "^3.0.2"
|
|
types-requests = "^2.27.7"
|
|
types-psycopg2 = "^2.9.6"
|
|
boto3 = "^1.20.40"
|
|
boto3-stubs = "^1.20.40"
|
|
moto = {version = "^3.0.0", extras = ["server"]}
|
|
backoff = "^1.11.1"
|
|
pytest-lazy-fixture = "^0.6.3"
|
|
prometheus-client = "^0.14.1"
|
|
pytest-timeout = "^2.1.0"
|
|
|
|
[tool.poetry.dev-dependencies]
|
|
yapf = "==0.31.0"
|
|
flake8 = "^3.9.2"
|
|
mypy = "==0.910"
|
|
|
|
[build-system]
|
|
requires = ["poetry-core>=1.0.0"]
|
|
build-backend = "poetry.core.masonry.api"
|