Nixpkgs: build during evaluation

[vcunat]

I was recently wondering why each Hydra eval of full nixpkgs now takes rougly one hour, and now I see there are apparently builds done during it. See https://hydra.nixos.org/jobset/nixos/gcc-7#tabs-errors (the branch only has a couple lines of changes when compared to master)

• [ ] find the culprit

[edolstra]

Oh, that's very bad...

[dezgeg]

At least one instance fixed in c88075682389b7c16a519503cb8ca1f16fb31757. Maybe Hydra could be fixed to not allow that.

[vcunat]

Not fixed. For the gcc-7 jobset I now worked around it by starting with release-small which doesn't seem to have this problem. Also, in the nixpkgs staging job this doesn't happen, so it must be something specific for release-combined. I see things like

defaultConfig = builtins.fromJSON (readFile "${pkgs.mattermost}/config/config.json")

[dezgeg]

staging doesn't show these because most of them are coming from NixOS modules and/or tests, e.g.: https://github.com/NixOS/nixpkgs/commit/dc5cd7800a004b9c58d0cdd5482d6980e3e47205 and https://github.com/NixOS/nixpkgs/commit/cb008da16755d1de08e930461eb8be742a3daabf.

Those ones showed up while trying to evaluate trunk-combined on aarch64, which fails because apparently the Hydra evaluator can't connect to the aarch64 build slave, only the Hydra queue runner can.

[dezgeg]

nix-instantiate nixos/tests/kubernetes/default.nix -A rbac does it as well. The expression that imports it to the release jobset is not evaluating, though, so the kubernetes tests aren't getting run by Hydra either.

[stale[bot]]

Hello, I'm a bot and I thank you in the name of the community for opening this issue.

To help our human contributors focus on the most-relevant reports, I check up on old issues to see if they're still relevant. This issue has had no activity for 180 days, and so I marked it as stale, but you can rest assured it will never be closed by a non-human.

The community would appreciate your effort in checking if the issue is still valid. If it isn't, please close it.

If the issue persists, and you'd like to remove the stale label, you simply need to leave a comment. Your comment can be as simple as "still important to me". If you'd like it to get more attention, you can ask for help by searching for maintainers and people that previously touched related code and @ mention them in a comment. You can use Git blame or GitHub's web interface on the relevant files to find them.

Lastly, you can always ask for help at our Discourse Forum or at #nixos' IRC channel.