!RROtHmAaQIkiJzJZZE:nixos.org

NixOS Infrastructure

383 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

Load older messages


SenderMessageTime
18 Aug 2021
@andi:kack.itandi-Was staging merged?22:51:05
@sternenseemann:systemli.orgsterniyes, it probably just has to instanitate everything and realize it is already cached?22:57:55
@sternenseemann:systemli.orgsterniyeah half already done22:58:42
21 Aug 2021
@lukegb:zxcvbnm.ninjalukegb (he/him) update-nixos-unstable.service is wedged again 20:08:25
@lukegb:zxcvbnm.ninjalukegb (he/him)https://p.lukegb.com/raw/EvidentlyGlowingBurro.png20:09:13
@sternenseemann:systemli.orgsterni changed their display name from sterni (he/him) to sterni[m].22:21:31
@sternenseemann:systemli.orgsterni changed their display name from sterni[m] to sterni.22:21:48
22 Aug 2021
@lukegb:zxcvbnm.ninjalukegb (he/him)Still stuck :)10:04:30
23 Aug 2021
@bachp:matrix.orgPascal Bach joined the room.13:14:36
@andi:kack.itandi-Would it make sense to pipe those prometheus alerts into this channel via alertmanager+any of the matrix bots?13:17:08
@vcunat:matrix.orgVladimír ČunátWe're mainly missing the logs. Historically I think these errors can often be fixed just by pushing into nixpkgs, but without the logs we have no idea what's wrong.13:18:28
@sandro:supersandro.deSandroWhy do we have nix store links in the docs? https://search.nixos.org/options?channel=unstable&show=boot.tmpOnTmpfs&from=0&size=50&sort=relevance&query=tmp15:17:08
@andi:kack.itandi-https://github.com/NixOS/nixos-search/issues/33515:22:55
@collares:matrix.orgcollares joined the room.19:03:03
@hexa:lossy.networkhexa
In reply to @lukegb:zxcvbnm.ninja
update-nixos-unstable.service is wedged again
How long do we wait before we explicltly mention people?
20:39:38
@hexa:lossy.networkhexa
In reply to @lukegb:zxcvbnm.ninja
update-nixos-unstable.service is wedged again
* How long do we wait before we start explicltly mentioning people?
20:39:46
@vcunat:matrix.orgVladimír Čunát I think we can start mentioning slowly: Amine Chikhaoui (has necessary access IIRC) 20:53:17
@hexa:lossy.networkhexabasically everyone on here? https://nixos.org/community/teams/infrastructure.html20:59:34
@vcunat:matrix.orgVladimír ČunátYes, that list might (still) be close to reality.21:10:38
@vcunat:matrix.orgVladimír Čunát
In reply to @andi:kack.it

build flags: -j2 -l2

Since when are our builders running just two cores per build? Not an issue just surprised to see this.

Actually, I wonder what kind of separation is there. I'd expect load to be shared (e.g. no VM-level separation), so load 2 is rather easy to get and you'll mostly run single-core.
21:49:17
@vcunat:matrix.orgVladimír Čunát
In reply to @andi:kack.it

build flags: -j2 -l2

Since when are our builders running just two cores per build? Not an issue just surprised to see this.

*

Actually, I wonder what kind of separation is there. I'd expect load to be shared (e.g. no VM-level separation), so load 2 is rather easy to get and you'll mostly run single-core.

It's the case where you'd want -l to be way higher than -j.

21:51:02
@princemachiavelli:matrix.orgprincemachiavelli joined the room.22:34:18
@princemachiavelli:matrix.orgprincemachiavelliLooks like /scratch is full on bastion. https://monitoring.nixos.org/prometheus/graph?g0.expr=node_filesystem_avail_bytes%7Bmountpoint%3D%22%2Fscratch%22%7D&g0.tab=0&g0.stacked=0&g0.range_input=2w22:35:08
@lukegb:zxcvbnm.ninjalukegb (he/him)filed https://github.com/NixOS/nixpkgs/issues/135484 and mentioned the infra github team23:22:57
24 Aug 2021
@grahamc:nixos.org@grahamc:nixos.orgm'onit00:59:58
@andi:kack.itandi-
In reply to @vcunat:matrix.org

Actually, I wonder what kind of separation is there. I'd expect load to be shared (e.g. no VM-level separation), so load 2 is rather easy to get and you'll mostly run single-core.

It's the case where you'd want -l to be way higher than -j.

Valid point. I wasn't thinking about that case. Perhaps worth seeing if the kernel can expose load per process namespace?
09:46:33
@vcunat:matrix.orgVladimír Čunát
In reply to @andi:kack.it
Valid point. I wasn't thinking about that case. Perhaps worth seeing if the kernel can expose load per process namespace?
And then we patch all the build systems? I'm more hopeful for a job-server... or us separating -l from -j.
09:49:36
@andi:kack.itandi-No, I would patch the way the nix sandbox works.09:50:43
@andi:kack.itandi-e.g. if you don't run enough work for two cores your load should not be >=209:51:04
@vcunat:matrix.orgVladimír ČunátI didn't think that linux namespaces allow modifying the load, but perhaps... I haven't given it much time.11:25:32

Show newer messages


Back to Room ListRoom Version: 6