7148704dd3
test: will this cancel?
CI TEST3 / lint (pull_request) Successful in 1m9s
CI TEST3 / unit-test (pull_request) Successful in 36s
CI TEST3 / mutation-test (pull_request) Successful in 1m4s
CI TEST3 / fuzz-test (pull_request) Failing after 55s
2026-03-17 20:04:05 -04:00
f31100b23a
test: try again, doubled the job capacity
CI TEST2 / unit-test (pull_request) Successful in 55s
CI TEST2 / lint (pull_request) Successful in 1m43s
CI TEST2 / fuzz-test (pull_request) Successful in 1m12s
CI TEST2 / mutation-test (pull_request) Successful in 1m1s
2026-03-17 20:03:23 -04:00
a9b157d4b2
test: does the previous CI check get canceled?
CI TEST / lint (pull_request) Successful in 51s
CI TEST / unit-test (pull_request) Successful in 26s
CI TEST / fuzz-test (pull_request) Successful in 1m3s
CI TEST / mutation-test (pull_request) Successful in 2m37s
2026-03-17 19:54:02 -04:00
9726670dea
feat: only one CI job at a time per PR
...
CI / lint (pull_request) Successful in 52s
CI / unit-test (pull_request) Successful in 26s
CI / fuzz-test (pull_request) Successful in 1m3s
CI / mutation-test (pull_request) Successful in 43s
This prevents the Gitea runner from getting clogged up with stale CI checks.
2026-03-17 19:51:19 -04:00
62bc15a979
refactor: rename lint.yml to ci.yml
...
The `lint.yml` workflow contains more than just linting jobs. Renaming it to `ci.yml`, which is more general, and common practice.
2026-03-17 19:49:21 -04:00
717408239b
chore: move from tools/dsa ( #1 )
...
CI / lint (push) Successful in 51s
CI / unit-test (push) Failing after 25s
CI / fuzz-test (push) Successful in 1m1s
CI / mutation-test (push) Successful in 42s
Moved the implementation of this hash table from `tools/dsa` #1 .
Reviewed-on: #1
Co-authored-by: M.V. Hutz <git@maximhutz.me >
Co-committed-by: M.V. Hutz <git@maximhutz.me >
2026-03-17 01:22:42 +00:00
