| 17 Aug 2021 |
 andi- | So perhaps related to those NAT64 changes or whatever it was that is new in the version? | 14:27:18 |
| andi- | * ~So perhaps related to those NAT64 changes or whatever it was that is new in the version?~ | 14:27:52 |
| andi- | * So perhaps related to those NAT64 changes or whatever it was that is new in the version? | 14:28:02 |
| 18 Aug 2021 |
 sterni (he/him) | is there any sort of policy for triggering evals in trunk-combined etc? | 13:21:19 |
| sterni (he/him) | the last eval this morning was aborted completely I think because tests didn't eval in the first place | 13:22:08 |
| sterni (he/him) | (at least so it seems) | 13:22:12 |
 Vladimír Čunát | I'm not aware of any. | 13:22:19 |
| Vladimír Čunát | I last evaluation 18h ago and period 24h. | 13:23:24 |
| Vladimír Čunát | * I see the last evaluation 18h ago and period 24h. | 13:23:28 |
| Vladimír Čunát | * I see the last successful evaluation 18h ago and period 24h. | 13:23:35 |
| sterni (he/him) | Last checked: 2021-08-18 00:23:44 | 13:23:39 |
| sterni (he/him) | hydra-eval-jobs returned exit code 1: (due to this issue: https://github.com/NixOS/nixpkgs/pull/134645) | 13:24:08 |
| Vladimír Čunát | Anyway, no problem triggering it now, as *-linux is idle. | 13:24:50 |
| sterni (he/him) | kk will do then | 13:25:02 |
| sterni (he/him) | oh you did :) | 13:25:14 |
 FRidh | Question: where can I find the nixos configuration of prometheus / grafana of https://monitoring.nixos.org ? | 14:00:00 |
| andi- | In reply to @FRidh:matrix.org
Question: where can I find the nixos configuration of prometheus / grafana of https://monitoring.nixos.org ? https://github.com/NixOS/nixos-org-configurations/blob/444a387257ed8c43974d20744de5785f91495249/delft/eris.nix | 14:02:37 |
| FRidh | In reply to @andi:kack.it
https://github.com/NixOS/nixos-org-configurations/blob/444a387257ed8c43974d20744de5785f91495249/delft/eris.nix thanks! | 14:04:59 |
| andi- |
build flags: -j2 -l2
Since when are our builders running just two cores per build? Not an issue just surprised to see this.
| 17:47:48 |
| sterni (he/him) | sure that that setting is not derivation specific? | 18:02:00 |
| andi- | I am pretty sure. I've built systemd locally with 24 jobs while the exact same derivation only builds with two on hydra. | 18:13:02 |
| andi- | (leading to a ~15min build time which isn't terrible but it slows down everything as it is a pretty famous dependency) | 18:13:45 |
| sterni (he/him) | hm yeah seems like the machines has MAX_BUILD_CORES=2 set | 18:27:25 |
| sterni (he/him) | it's always a bit difficult to balance max jobs and build cores which is probably the intent here | 18:27:54 |
| andi- | Yeah. I actually think it is the right choice (perhaps for 4/4 would also be fine) for regular builds. | 18:29:34 |
| andi- | If you really need more we have big-parallel etc. for those jobs | 18:29:45 |
| Vladimír Čunát | Yes, I've heard of the 2-core setting, but I'm not sure if it applies to all builders (without big-parallel). | 19:03:50 |
| sterni (he/him) | trunk has 103554 queued builds? | 22:19:58 |
| andi- | Was staging merged? | 22:51:05 |
| sterni (he/him) | yes, it probably just has to instanitate everything and realize it is already cached? | 22:57:55 |
