Skip to content

v0.3.1

Choose a tag to compare

@github-actions github-actions released this 16 Nov 17:58
· 1 commit to main since this release
78c0be0

Moving to 0.3.1

This version adds a new rule, mojo-build-per-test, to the tests group. Like the rest of that group, it is deny by default. It reports a pixi task, CI step or script that runs mojo build on more than 3 test files. Wrappers that pass their arguments on to mojo build count too, such as a compile() shell function or scripts/mojo-build.sh. Building several programs is not reported, only test files.

A project that builds each test file into its own binary will now fail its customs job. In the change that moves the pin, either build the tests once, or set the rule to warn in pixi.toml:

[tool.customs.lints]
# Why it stays as it is.
mojo-build-per-test = "warn"

Its threshold is mojo-build-per-test-threshold (default 3) under [tool.customs].

Also in this version:

  • A test file, for both per-test rules, must now contain a def test_ at its top level when the file exists. Programs under tests/, such as drivers or files that must fail to compile, are not counted.
  • A task that calls something already reported is still reported for the test files it runs or builds itself.

What's Changed

  • mojo-build-per-test: report building more than 3 test files one by one; 0.3.1 by @winding-lines in #7

Full Changelog: v0.3.0...v0.3.1