!lymvtcwDJ7ZA9Npq:lix.systems

Lix Development

255 Members
(Technical) development of Lix, the package manager, a Nix implementation. Please be mindful of ongoing technical conversations in this channel.100 Servers

You have reached the beginning of time (for this room).


SenderMessageTime
9 Oct 2024
@kfears:matrix.orgKFears (tragedy arc)
In reply to @jade_:matrix.org
https://git.lix.systems/lix-project/lix/src/370ac940dd7816ad4052fafa4e0f8d17784fa16b/src/libfetchers/fetchers.cc#L135-L148 type of compat code
That doesn't seem too bad
21:21:31
@jade_:matrix.orgjade_no, it is ridiculous actually21:21:43
@jade_:matrix.orgjade_it is that a test is relying on our stderr output21:21:48
@kfears:matrix.orgKFears (tragedy arc)I mean, it's a stupid block of code that shouldn't really be here, but it's a fairly minor block code21:21:57
@jade_:matrix.orgjade_ we cannot change our logs or else we might break a test 21:22:09
@jade_:matrix.orgjade_ that's ridiculous 21:22:14
@kfears:matrix.orgKFears (tragedy arc)
In reply to @jade_:matrix.org
it is that a test is relying on our stderr output
Well, that part is just insanity
21:22:17
@kfears:matrix.orgKFears (tragedy arc)Wait, what does "Nixpkgs fileset lib tests" mean?21:22:47
@k900:0upti.meK900 lib.filesets 22:40:44
@k900:0upti.meK900Which is also broken for another reason now 22:40:51
@k900:0upti.meK900So that's fun 22:40:54
@jade_:matrix.orgjade_wait did we regress it or did nixpkgs regress it?22:51:42
@jade_:matrix.orgjade_if we regressed it, fucking hell :(22:51:46
@k900:0upti.meK900Neither 22:53:29
@k900:0upti.meK900It was always broken 22:53:33
@jade_:matrix.orgjade_oh, well, problem in user code, not my problem thankfully22:53:59
@k900:0upti.meK900https://github.com/NixOS/nix/issues/1150322:54:15
@k900:0upti.meK900If you want the full story 22:54:21
@k900:0upti.meK900And the short version is that we can't actually use filesets for anything a user may want to nixos-install22:54:52
@k900:0upti.meK900And fixing it will require breaking existing eval 22:55:28
@jade_:matrix.orgjade_pfft22:55:50
@jade_:matrix.orgjade_oh no is this reliance on toString of a path value22:56:34
@jade_:matrix.orgjade_that would be both hilarious and unsurprising if so22:56:53
10 Oct 2024
@jade_:matrix.orgjade_

raitobezarius: it appears that the buildbot status reporter is not just broken in terms of usability but dangerously broken in terms of functionality: it reports Verified+1 probably on nix-eval completion before finishing building things.

also we have several instances of some kind of nixos test getting wedged in unknown ways, which might be a lix bug or something else haunted: https://buildbot.lix.systems/#/builders/1/builds/6000

really have to catch it in the act and gdb it i reckon

02:55:52
@vigress9:matrix.orgV. 🏳️‍⚧️
In reply to @jade_:matrix.org

you can use --keep-failed and it will keep the build-dir that failed and give you more meson logs, but...

this is really weird that it's consistently broken on your machine and on gha and that not really anyone else seems to be hitting it

I'm gonna try bisecting from 2.91
06:30:56
@aloisw:kde.orgaloisw
In reply to @k900:0upti.me
https://github.com/NixOS/nix/issues/11503
Why am I not surprised that the userspace chroot does not actually act like a chroot.
08:24:48
@raitobezarius:matrix.orgraitobezariusit's in my todolist to deal with the buildbot stuff today10:03:15
@vigress9:matrix.orgV. 🏳️‍⚧️Redacted or Malformed Event11:42:48
@vigress9:matrix.orgV. 🏳️‍⚧️Redacted or Malformed Event11:43:14
@vigress9:matrix.orgV. 🏳️‍⚧️Redacted or Malformed Event11:45:10

Show newer messages


Back to Room ListRoom Version: 10