Alexander Bayandin 2ec8dff6f7 CI(build-and-test-locally): set session-timeout for pytest (#10831) ...

## Problem

Sometimes, a regression test run gets stuck (taking more than 60
minutes) and is killed by GitHub's `timeout-minutes` without leaving any
traces in the test results database.
I find no correlation between this and either the build type, the
architecture, or the Postgres version.

See: https://neonprod.grafana.net/goto/nM7ih7cHR?orgId=1

## Summary of changes
- Bump `pytest-timeout` to the version that supports `--session-timeout`
- Set `--session-timeout` to (timeout-minutes - 10 minutes) * 60 seconds
in Attempt to stop tests gracefully to generate test reports until they
are forcibly stopped by the stricter `timeout-minutes` limit.

2025-02-15 10:34:11 +00:00

..

actions

Enable sanitizers for postgres v17 (#10401)

2025-02-06 12:53:43 +00:00

ISSUE_TEMPLATE

[infra/notes] impr: add issue types to issue templates (#10018)

2025-01-31 06:29:06 +00:00

PULL_REQUEST_TEMPLATE

Migrate links from wiki to notion (#5862)

2023-11-14 15:36:47 +00:00

workflows

CI(build-and-test-locally): set session-timeout for pytest (#10831)

2025-02-15 10:34:11 +00:00

actionlint.yml

Move cargo-deny into a separate workflow on a schedule (#10289)

2025-01-31 13:42:59 +00:00

file-filters.yaml

Move cargo-deny into a separate workflow on a schedule (#10289)

2025-01-31 13:42:59 +00:00

pull_request_template.md

Remove checklist from the PR template (#9702)

2024-11-11 17:01:02 +00:00