The job timeout value seems to be hard-coded and does not adapt to the amount of tests being modified in a single PR. PRs that change core features might need to update several test files as well as introduce new ones. The tests itself do not timeout, but the job does.

https://s3.amazonaws.com/clickhouse-test-reports/65277/41a4a97ca3c47bc4420b9247572f937569b98e6f/stateless_tests_flaky_check__asan_.html