NixOS Infrastructure | 382 Members | |
| Next Infra call: 2024-07-11, 18:00 CEST (UTC+2) | Infra operational issues backlog: https://github.com/orgs/NixOS/projects/52 | See #infra-alerts:nixos.org for real time alerts from Prometheus. | 118 Servers |
| Sender | Message | Time |
|---|---|---|
| 14 Aug 2021 | ||
| if we want to eke all the life we can from wendy then we should remove the big-parallel required feature and add features for processor extensions to all the builders that do have them | 14:40:36 | |
| but at the moment: the work wendy is doing could be done faster and better by one of the other workers | 14:41:14 | |
My understanding is that wendy got switched to big-parallel jobs exactly in order to avoid pytorch. | 15:35:53 | |
| Yeah, but then I made pytorch big-parallel because the build takes a long time and is parallelisable xD | 15:43:18 | |
| Oh, I didn't notice the reply and found out independently. | 15:51:25 | |
| From what I've seen, wendy really is more trouble than worth. | 15:53:03 | |
| 15 Aug 2021 | ||
grahamc (he/him): can I get a new hydra jobset ala staging (with... whatever shares are appropriate) pointed at https://github.com/lukegb/nixpkgs.git xcrypt? This is for https://github.com/NixOS/nixpkgs/issues/112371 | 02:16:50 | |
In reply to @lukegb:zxcvbnm.ninja I wonder if building all individual packages is an overkill. Only relatively few packages use the library, I think; Arch list: https://archlinux.org/todo/libxcrypt-rebuild/ It might make sense to start just locally. Or do a -small jobset and then (using that from cache) try those packages locally. A potential risk: I wonder if some build scripts might just silently turn off some features when failing to find libcrypt (or even try to only find it during runtime). But I'd hope the impact won't be significant here. | 08:25:53 | |
Anyway, gcc won't build, so there's not much to do yet :-)
| 09:35:52 | |
*
Anyway, gcc won't build, so there's not much to rebuild yet :-)
| 09:36:33 | |
| I guess my point was: it's going to be a full rebuild anyway, even of unrelated packages | 10:50:29 | |
| For the same reason as glibc version bumps are full rebuilds | 10:50:41 | |
| I guess maybe I'll just merge it into staging and then we can fix it there rather than have a new jobset if we're reluctant to do that | 11:07:27 | |
In reply to @vcunat:matrix.orgOh right, that's fixed locally, I haven't pushed it yet | 11:09:58 | |
| Yes, it will be a full rebuild either way, but the extra jobset would serve to find breakages, not to utilize those binaries (because staging/next is somewhere else or would move in the meantime anyway). | 11:44:47 | |
| Right now Hydra is fully utilized by staging-next - and I believe it should take precedence even if I created your jobset immediately. (the current iteration has been stabilizing for more than two weeks already) | 11:50:04 | |
| One of the problems we're going to run into though is that bootstrapping it is hard, because they don't ship tarball releases | 12:52:45 | |
| 16 Aug 2021 | ||
| lukegb (he/him): if you push it, I can build e.g. that list of packages from Arch to test. | 16:15:33 | |
... and after those pass, I suspect it might be ready to merge to staging anyway. | 16:16:27 | |
| I got stuck untangling the build with gcc in a satisfactory way | 16:46:28 | |
| I might try and ask upstream to start making "real" releases | 16:46:44 | |
| oh, there's already a bug from the gentoo folks | 17:26:53 | |
| 20:40:50 | ||
| https://github.com/NixOS/nixpkgs/pull/133375#issuecomment-899806058 | 23:32:37 | |
| fails to build because it cannot resolve … anything?
| 23:43:29 | |
| 17 Aug 2021 | ||
| works if I prefetch the tarball | 00:33:10 | |
| Perhaps the same as https://github.com/NixOS/nix/issues/5089 | 10:37:42 | |
| Also works If i revert the c-ares bump | 11:53:57 | |
| Was that failure on darwin? | 14:16:28 | |
| I reproduced that on my x86_64 desktop | 14:21:54 | |