!UNVBThoJtlIiVwiDjU:nixos.org

Staging

341 Members
Staging merges | Running staging cycles: https://github.com/NixOS/nixpkgs/pulls?q=is%3Apr+is%3Aopen+head%3Astaging-next+head%3Astaging-next-25.11 | Review Reports: https://malob.github.io/nix-review-tools-reports/111 Servers

Load older messages


SenderMessageTime
7 Oct 2025
@k900:0upti.meK900istg pyside15:38:07
@k900:0upti.meK900I'm gonna do a violence15:38:23
@willi:butz.cloudWilli Butzhttps://gist.github.com/WilliButz/afd8ca68c45c5e6a96216f6b92658d2315:38:29
@grimmauld:grapevine.grimmauld.deGrimmauld (migrated to @grimmauld:m.grimmauld.de)HUH15:38:47
@k900:0upti.meK900o7 asan15:38:54
@grimmauld:grapevine.grimmauld.deGrimmauld (migrated to @grimmauld:m.grimmauld.de)nikstur ran into that too, but after disabling parallel checking it went away for him15:39:24
@grimmauld:grapevine.grimmauld.deGrimmauld (migrated to @grimmauld:m.grimmauld.de)i hate asan15:39:27
@grimmauld:grapevine.grimmauld.deGrimmauld (migrated to @grimmauld:m.grimmauld.de)the best part: i can't repro that one on my machine15:39:57
@grimmauld:grapevine.grimmauld.deGrimmauld (migrated to @grimmauld:m.grimmauld.de)like, at all15:40:00
@vcunat:matrix.orgvcunatasan has interactions with PIE, or why the regression?15:40:05
@vcunat:matrix.orgvcunatThough the log suggest that kernel is to blame 🤯15:41:21
@aloisw:julia0815.de@aloisw:julia0815.de PIE was already in the last staging-next, right? 15:41:31
@grimmauld:grapevine.grimmauld.deGrimmauld (migrated to @grimmauld:m.grimmauld.de)yep15:41:41
@grimmauld:grapevine.grimmauld.deGrimmauld (migrated to @grimmauld:m.grimmauld.de) tbh if asan+pie causes trouble depending on host kernel, i'd vote to just skip that check 15:42:04
@grimmauld:grapevine.grimmauld.deGrimmauld (migrated to @grimmauld:m.grimmauld.de) * tbh if asan+pie causes trouble depending on build kernel, i'd vote to just skip that check 15:42:20
@willi:butz.cloudWilli Butzhuh. I can't on my local workstation. the above happened on a hetzner ax162 so maybe ignore for now15:43:00
@vcunat:matrix.orgvcunatDepends on your kernel perhaps.15:43:17
@willi:butz.cloudWilli Butzhetzner 6.12, local 6.1615:44:03
@vcunat:matrix.orgvcunatDoesn't seem suspicious.15:44:23
@vcunat:matrix.orgvcunatHydra's builders use 6.12, BTW.15:45:13
@vcunat:matrix.orgvcunat(stable NixOS default generally)15:45:23
@grimmauld:grapevine.grimmauld.deGrimmauld (migrated to @grimmauld:m.grimmauld.de)i am on 6.12 here15:45:23
@vcunat:matrix.orgvcunatI'm trying with 6.6 now.15:46:12
@willi:butz.cloudWilli Butz ah, so the builder runs some "hardened" variant, not sure if its just linuxPackages_6_12_hardened 15:49:36
@vcunat:matrix.orgvcunatThat might be it.15:50:16
@vcunat:matrix.orgvcunatThis kind of layout changes feel potentially useful for hardening.15:50:42
@vcunat:matrix.orgvcunat

Shadow memory range interleaves with an existing memory mapping.

15:51:08
@vcunat:matrix.orgvcunatStill, if the test is unreliable like this, I'm perfectly fine with skipping it.15:51:57
@vcunat:matrix.orgvcunatIt's the kind of thing that might make sense to keep upstream, as e.g. their CI will be known not to suffer from the hardening. But not suitable as a default in a distro.15:53:00
@willi:butz.cloudWilli Butzjust saw that it is part of the logs 🤦 https://gist.github.com/WilliButz/afd8ca68c45c5e6a96216f6b92658d23#file-build-log-L101215:53:59

Show newer messages


Back to Room ListRoom Version: 6