!RROtHmAaQIkiJzJZZE:nixos.org

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

Load older messages


SenderMessageTime
12 Feb 2025
@raitobezarius:matrix.orgraitobezariustesting phase of programs built may trigger SIGABRT on purpose ;-)00:14:18
@hexa:lossy.networkhexa
(gdb) bt full
#0  0x00007ffff7a4c16c in ?? ()
No symbol table info available.
#1  0x00000000004273b0 in ?? ()
No symbol table info available.
#2  0x3693e7cdb4796900 in ?? ()
No symbol table info available.
#3  0x0000000000000006 in ?? ()
No symbol table info available.
#4  0x00007ffff79b1b80 in ?? ()
No symbol table info available.
#5  0x00007fffffffd8c0 in ?? ()
No symbol table info available.
#6  0x0000000000000000 in ?? ()
No symbol table info available.
00:15:07
@arianvp:matrix.orgArianAh lol yeh00:15:07
@hexa:lossy.networkhexa🙂 00:15:08
@hexa:lossy.networkhexabut why do those leak into the host, while most other crashes do not?00:15:58
@hexa:lossy.networkhexa
     11 2024-12-24
    125 2025-01-24
    182 2025-01-25
     93 2025-01-26
    713 2025-01-27
    275 2025-01-28
     67 2025-01-29
    400 2025-01-30
    185 2025-01-31
    140 2025-02-01
     63 2025-02-02
     92 2025-02-03
     68 2025-02-04
    777 2025-02-05
   1173 2025-02-06
    429 2025-02-07
     16 2025-02-08
    255 2025-02-09
    724 2025-02-10
   1415 2025-02-11
00:16:43
@hexa:lossy.networkhexathe number of crashes we see per day00:17:02
@hexa:lossy.networkhexa* the number of crashes we see per day on a single builder00:17:08
@hexa:lossy.networkhexamost have no corefile00:17:17
@9lore:tchncs.de@9lore:tchncs.deHi, just curious https://hydra.nixos.org/build/288757617 is this stuck? Will it timeout at some point?00:17:50
@arianvp:matrix.orgArianI guess filtering to just the ones we're comm=nix-daemon makes sense 00:17:52
@raitobezarius:matrix.orgraitobezarius
In reply to @hexa:lossy.network
but why do those leak into the host, while most other crashes do not?
cgroups setup
00:18:07
@raitobezarius:matrix.orgraitobezarius(or I misunderstood your remark)00:18:21
@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

Show newer messages


Back to Room ListRoom Version: 6