walnux/.github/workflows
Lup Yuen Lee 4cfdaa0105 CI: Kill CI Test after 2 hours
CI Test will sometimes run for 6 hours (before getting auto-terminated by GitHub):
- https://github.com/apache/nuttx/issues/14808
- https://github.com/apache/nuttx/issues/14680

This is a problem because:
- It will increase our usage of GitHub Runners. Which may overrun the [GitHub Actions Budget](https://infra.apache.org/github-actions-policy.html) allocated by ASF.
- Suppose right after CI Test there's another build. If CI Test runs for all 6 hours, then the build after CI Test will never run.

For this PR: We assume that Every CI Job (e.g. risc-v-05) will complete normally within 2 hours. If any CI Job exceeds 2 hours: This PR will kill the CI Test Process `pytest` and allow the next build to run.
2024-11-19 17:17:43 +08:00
..
arch.yml CI: Enable builds for msys2, msvc, arm-08, arm-10, arm-13 for Complex PRs 2024-11-02 09:25:12 -03:00
build.yml CI: Kill CI Test after 2 hours 2024-11-19 17:17:43 +08:00
check.yml ci: add Python linter to check 2024-10-15 15:01:07 +02:00
doc.yml ci: documentation workflow is now only triggered when the Documentation subdirectory has modifications, and does not build pdfs. 2024-10-17 09:04:50 +08:00
docker_linux.yml tools/ci/docker/linux/Dockerfile: Restarting the Docker-Linux workflow a new attempt 2024-09-02 14:11:51 -04:00
issue_labeler.yml ISSUE_TEMPLATE: fix missing labels 2024-10-21 18:04:27 +02:00
labeler.yml build(deps): bump codelytv/pr-size-labeler from 1.10.0 to 1.10.1 2024-09-23 14:37:02 +08:00
lint.yml build(deps): bump github/super-linter from 6 to 7 2024-09-07 12:08:11 +08:00