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
..
actions	free disk space action added to fix docker image build issue	2023-12-08 14:42:17 +01:00
ISSUE_TEMPLATE	ISSUE_TEMPLATE: fix missing labels	2024-10-21 18:04:27 +02:00
linters	.github/linters: Ignore E704 warning	2024-11-17 08:31:08 -03:00
workflows	CI: Kill CI Test after 2 hours	2024-11-19 17:17:43 +08:00
dependabot.yml	chore: Included githubactions in the dependabot config	2022-06-19 11:43:10 +08:00
gcc.json	.github/gcc.json: Fix space/tab inconsistency	2022-04-12 13:43:06 +08:00
labeler.yml	.github/labeler.yml: add missing drivers label	2024-11-03 20:54:39 +08:00
nxstyle.json
PULL_REQUEST_TEMPLATE.md	Contributing and PR template fix.	2024-10-12 08:12:05 +08:00
SECURITY.md	docs: Include released 10.x and 11.x versions under security policy.	2022-11-21 10:06:31 +01:00