# evaluator_initial_heap_size is basically equivalent to GC_INITIAL_HEAP_SIZE and defaults to 384MiB
    # evaluator_max_memory_size is… "If our RSS exceeds the maximum, exit. The master will start a new process.". defaults to 4096 (I assume MiB)
    # evaluator_workers is how many parallel evaluator workers are used. defaults to 1
    # max_concurrent_evals defines how many evaluations are run concurrently. defaults to 4
    extraConfig = ''
      email_notification = 1
      evaluator_max_memory_size = 4096
      evaluator_initial_heap_size = ${toString (2 * 1024 * 1024 * 1024)}
      max_output_size = ${toString (16 * 1024 * 1024 * 1024)}
      max_concurrent_evals = 3
      evaluator_workers = 4

In reply to @sandro:supersandro.de
Do I want this or does that slow down things? I have the feeling that sometimes jobs just stale a longer time which may be related to that.

In reply to @sandro:supersandro.de
Also is warning: 7 concurrent database updates; PostgreSQL may be stalled normal? postgres itself seems to be happy.

In reply to @janne.hess:helsinki-systems.de
I don't think it makes any sense. It pushes the required store paths to builders anyway and substituting from itself will never yield any success

In reply to @janne.hess:helsinki-systems.de
I don't think it makes any sense. It pushes the required store paths to builders anyway and substituting from itself will never yield any success

How do I reset an error message like?

Aborted: error: a 'x86_64-linux' with features {gccarch-skylake} is required to build '/nix/store/fykll0wrfya0zqw51nsi9jbi0lasyfaa-closure-info.drv', but I am a 'x86_64-linux' with features {gccarch-haswell, gccarch-ivybridge, gccarch-sandybridge, gccarch-westmere} (log, raw, tail)}

Clear failed builds cache does not seem to do anything. Also why is hydra trying to build this on localhost?

My hydra machines file looks like localhost x86_64-linux - 4 5 gccarch-haswell,gccarch-ivybridge,gccarch-sandybridge,gccarch-westmere - -

In reply to @cole-h:matrix.org
You're looking for an "aggregate" job. There are some examples in Nixpkgs, I believe (look for `release.nix` or similarly-named files in `nixos/`). Also present in the Nix (the tool) flake, and probably the Hydra flake / repo as well.