diff options
| author | Wolfgang Walther <walther@technowledgy.de> | 2025-05-29 18:30:34 +0200 |
|---|---|---|
| committer | Wolfgang Walther <walther@technowledgy.de> | 2025-06-02 09:12:19 +0200 |
| commit | a7f4e0f9ae31e5ec90dd6ca7d5465d4ed97ee099 (patch) | |
| tree | 292e1c466216be9970b685d1c1118a9c02791fbc /pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch | |
| parent | f87dac4be32235f7a7409eaf3faaa10213264e34 (diff) | |
lib/tests: avoid full rebuild when only maintainers change
The vast majority of CI jobs to build the lib tests are caused by
changes in the maintainer list. In this case, we currently run the full
test-suite which takes 3-4 minutes. By moving the maintainers and teams
tests out of the test-with-nix file, we save almost all of that.
Building only those two tests on a change is almost instant. This only
works, because we previously enabled cachix for the workflow.
Note, that these tests are not actually run with both nix versions, even
though they were listed in the "test with specific nix version" file.
That's because we only differ in the nix version run *inside* the
sandbox, but not doing the outer build.
Since this file seems to be re-used by NixOS/nix' CI, this is
technically a small loss in coverage for that repo, but nixpkgs CI
considerations outweigh that. But because of this, I left the other
non-nix-version-specific tests in that file.
Diffstat (limited to 'pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch')
0 files changed, 0 insertions, 0 deletions