!RROtHmAaQIkiJzJZZE:nixos.org

NixOS Infrastructure

381 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.116 Servers

Load older messages


SenderMessageTime
12 Feb 2025
@hexa:lossy.networkhexalikely after 2 hours of silence00:18:29
@hexa:lossy.networkhexa raitobezarius: the question was: why do some few have corefiles, but most do not, when we're all running them in cgroups 00:19:13
@hexa:lossy.networkhexa * raitobezarius: the question was: why do some few have corefiles, but most do not, when we're all running them in the build sandbox 00:19:23
@raitobezarius:matrix.orgraitobezariuscorefiles are pruned00:19:28
@hexa:lossy.networkhexayes, but even new crashes have none 😄 00:19:39
@arianvp:matrix.orgArianSystemd deletes them after a while00:19:41
@raitobezarius:matrix.orgraitobezariusmaybe the vacuum algorithm is weird00:19:53
@raitobezarius:matrix.orgraitobezariusalso corefiles cannot always be obtained00:20:08
@raitobezarius:matrix.orgraitobezariussome crashes simply does not come with corefiles00:20:12
@hexa:lossy.networkhexayeah, I kinda expected it to be a sandboxing limitation that we get none00:20:30
@raitobezarius:matrix.orgraitobezarius https://man7.org/linux/man-pages/man5/core.5.html 00:20:30
@hexa:lossy.networkhexawould also be ridiculuous to store that many 😄 00:20:41
@arianvp:matrix.orgArianPID namespace should isolate coredumps yeh00:21:15
@arianvp:matrix.orgArian @raitobezarius:matrix.org: it's just a tmpfiles rule iirc. 00:22:06
@arianvp:matrix.orgArianAnyhow I guess core dumps in the build sandbox are less interesting. We're interested in coredumps of nix-daemon. Still weird they show up in the journal though 00:23:07
@erin:owo.meerin "nepeat" computer breaker joined the room.01:47:51
@arcayr:mischief.expertarcayr joined the room.02:51:50
@Ericson2314:matrix.orgJohn Ericson hexa (signing key rotation when): so I can easily just make hydra ignore lines that don't parse as JSON, but I am less sure whether that is good or just treating symptons 03:00:42
@Ericson2314:matrix.orgJohn Ericsonthe underlying error message about x86_64-darwin no in suported features also looked sketchy03:00:59
@hexa:lossy.networkhexaI just posted that to show where it previously left off03:01:44
@hexa:lossy.networkhexaIdeally we could see that nix-eval-jobs sent broken JSON and send that upstream03:02:14
@hexa:lossy.networkhexa
In reply to @hexa:lossy.network
I just posted that to show where it previously left off
That is to say I am not sure how related it is
03:02:54
@Ericson2314:matrix.orgJohn EricsonOK03:03:36
@Ericson2314:matrix.orgJohn EricsonI will not read too much into that error message then :)03:03:45
@hexa:lossy.networkhexa
In reply to @Ericson2314:matrix.org
the underlying error message about x86_64-darwin no in suported features also looked sketchy
Maybe I misunderstood where you saw that
03:04:01
@Ericson2314:matrix.orgJohn Ericsonhttps://github.com/NixOS/hydra/issues/143703:04:34
@Ericson2314:matrix.orgJohn Ericsonoh unsupported system, not supported features03:04:40
@hexa:lossy.networkhexaerror: Unsupported system: aarch64-darwin03:04:43
@Ericson2314:matrix.orgJohn Ericsonyeah03:07:07
@Ericson2314:matrix.orgJohn Ericsonis that an expected eval failure?03:07:22

Show newer messages


Back to Room ListRoom Version: 6