mirror of
https://github.com/nim-lang/Nim.git
synced 2026-09-17 10:34:53 +00:00
1109fc4f83
The Microsoft-hosted Azure agents are 2-core; the GitHub-hosted runners are 4-core (3-core on macOS arm64). Measured on an identical `koch boot -d:release` against our own Docs CI, the GitHub runners are ~2.3x faster: Linux boot 8.2 min -> 4.5 min Windows boot 11.4 min -> 4.9 min macOS boot 4.2 min -> 1.7 min csources 2.0 min -> 0.8 min `.github/workflows/ci_main.yml` keeps the same six jobs, the same runner images, the same dependency installation and the same `ci/funs.sh` entry points, so this is a move, not a redesign. Differences forced by the platform: * `[skip ci]` is handled natively by GitHub, so the `nimIsCiSkip` step and the `skipci` variable that gated every step are gone. `nimIsCiSkip` stays in `ci/funs.sh` for the version branches. * `SYSTEM_ACCESSTOKEN` is gone: `testament/azure.nim` activates on `TF_BUILD`, which is unset here, so it no-ops. This also removes a flake source, where a failure to create the Azure test run cancelled an otherwise green job. * `concurrency: cancel-in-progress` replaces Azure's `pr.autoCancel`. * `NIM_TESTAMENT_BATCH` defaults to `_` explicitly: a matrix-derived env var is set to the empty string rather than left unset, so `getEnv`'s default would not have applied. `disabled: "azure"` was the only way to skip a test on the main pipeline, so add `disabled: "github"` (`isGithubActions`) to replace it; `azure` is kept as deprecated, alongside `travis` and `appveyor`. Two manual steps remain: disabling the Azure pipeline definition, and pointing the required status checks at the new job names. --------- Co-authored-by: ringabout <43030857+ringabout@users.noreply.github.com>
This directory contains the test cases.
Each test must have a filename of the form: t*.nim
Note: Testament is only aware of tests under a directory (eg tests/foo/) and will ignore
top-level tests like tests/tbar.nim.
Specs
Each test can contain a spec in a discard """ ... """ block.
Check out the parseSpec procedure in the specs module for a full and reliable reference
action
Specifies what action this test should take.
Default: run
Options:
compile- compiles the module and fails the test if compilations fails.run- compiles and runs the module, fails the test if compilation or execution of test code fails.reject- compiles the module and fails the test if compilation succeeds.
There are certain spec keys that imply run, including output and
outputsub.
Categories
Each folder under this directory represents a test category, which can be
tested by running koch tests pcat <category> (or cat to avoid parallel
testing, which is slower).
The folder dll contains simple DLL tests.
The folder realtimeGC contains a test for validating that the realtime GC
can run properly without linking against the nimrtl.dll/so.