!VRULIdgoKmKPzJZzjj:nixos.org

Nix Hackers

890 Members
For people hacking on the Nix package manager itself189 Servers

Load older messages


SenderMessageTime
14 Apr 2025
@dramforever:matrix.orgdramforeverWhatever's generating config.nix didn't expect the tests to be able to run on cross10:30:48
@dramforever:matrix.orgdramforever it's tests/functional/meson.build, but i don't know meson... 10:34:44
@dramforever:matrix.orgdramforever actually wait a second should we be running x86-32 builds? can we just run x86-64 builds in the tests? 10:36:56
@dramforever:matrix.orgdramforevermore generally if building with (build = B, host = H) and H is runnable on B then run checks and inside the checks we run builds with system = B instead of system = H. does this work? just an idea10:38:01
@dramforever:matrix.orgdramforeverbonus: ... it seems to fix the gc-auto problem as well?10:43:57
@aloisw:julia0815.de@aloisw:julia0815.deOh so this is the nested x86_32 sandbox disallowing x86_64 syscalls? That would totally make sense.10:44:00
@dramforever:matrix.orgdramforeverbooo that one also doesn't satisfy the seccomp10:49:49
@dramforever:matrix.orgdramforever* booo that one also doesn't satisfy the seccomp rules10:49:50
@dramforever:matrix.orgdramforeveri was looking on the issue tracker and apparently it's possible to get it without cross? https://github.com/NixOS/nix/issues/1128412:21:01
@dramforever:matrix.orgdramforeverbut that's also, like, a year ago, so maybe it's just an old bug12:23:06
@dramforever:matrix.orgdramforeverdoes anyone else want to make a issue report for the SIGSYS/"Bad system call" bug12:27:45
@dramforever:matrix.orgdramforeveri can't repro this so i'm going to assume this is just an old bug12:45:00
@dramforever:matrix.orgdramforeveror maybe wsl specific12:45:17
@dramforever:matrix.orgdramforeverat least it's not this sigsys one12:45:22
@dramforever:matrix.orgdramforever* or maybe wsl specific or single user specific12:45:34
@zorzem:matrix.orgzorzem changed their profile picture.17:05:34
15 Apr 2025
@noskcaj:matrix.org@noskcaj:matrix.org left the room.21:30:51
16 Apr 2025
@mschwaig:matrix.orgMartin SchwaighoferI have a couple of things that I'd like to bring up, which I am not sure if the triage meeting is the appropriate place for. Is that even happening today? The issues in question are https://github.com/NixOS/nix/issues/13037 https://github.com/NixOS/nix/issues/13036 and https://github.com/mschwaig/laut/issues/5#issuecomment-2809751534. The third one is not even in the Nix repo, but it's something I would like to implement and eventually upstream if it ends up actually working.16:59:28
@ivan_ermakov:matrix.orgDeus_YI_∞ changed their display name from dev_el_∞ to deus_el_∞.22:49:38
@ivan_ermakov:matrix.orgDeus_YI_∞ changed their display name from deus_el_∞ to Deus_YI_∞.22:52:09
17 Apr 2025
@skynet1197900:matrix.orgskynet joined the room.00:16:14
@dramforever:matrix.orgdramforeverwas going through my stuff and discovered that afaict the cross from x86_64 to x86 with tests SIGSYS bug hasn't been filed. here it is: https://github.com/NixOS/nix/issues/1304204:02:22
@mmkaram:matrix.org@mmkaram:matrix.org left the room.04:34:40
@Ericson2314:matrix.orgJohn Ericson https://github.com/joshlf/gherrit my friend just open sourced this, CC Mic92 17:57:31
@Ericson2314:matrix.orgJohn Ericsonit would be very nice to replace that "depends on" bot with something more sophisticated17:58:15
@joerg:thalheim.ioMic92 John Ericson: I suppose it depends on the someone restacking pull requests once something is merged manually? 18:07:42
@Ericson2314:matrix.orgJohn Ericson Mic92: just was told it is a client-side-only thing, so yes I think you are right 18:08:22
@joerg:thalheim.ioMic92I don't think anyone is opposed if you would use that. It can probably still be combined with the CI statuses from dpulls18:10:51
18 Apr 2025
@void68:matrix.orgvoid joined the room.02:16:31
@winter:catgirl.cloudWinter joined the room.08:57:54

Show newer messages


Back to Room ListRoom Version: 6