Closed roberth closed 1 week ago
Indeed I discussed just this sort of change with @tfc recently, and I'd take a slightly different architectural approach: instead of including environment-dependent setup/teardown, source
the script itself from each environment. WDYT?
instead of including environment-dependent setup/teardown,
source
the script itself from each environment. WDYT?
The implementation and benefit of this idea are unclear to me.
I have not changed the architecture to keep the diff manageable, so I'd like to proceed with this and refactor later.
Discussed in Nix maintainer meeting:
noGC
etc. outputs separately as well, currently they're only in Hydra jobsThis pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/2024-06-17-nix-team-meeting-minutes-153/47186/1
@roberth IMO you can self-merge once it's all green.
The extra swap appears to handle the extra evaluations with no significant slowdown :tada:
This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/2024-06-24-nix-team-meeting-minutes-155/47739/1
Motivation
By running the functional tests also in a mostly normal NixOS environment, we increase our test coverage.
This reproduces
4813 (see
timeout.sh
)It also allows for testing
Context
Rewrite of most of #7778
Possible follow-ups:
sudo
action in the functional testsPriorities and Process
Add :+1: to pull requests you find important.
The Nix maintainer team uses a GitHub project board to schedule and track reviews.