Lix Development | 429 Members | |
| (Technical) development of Lix, the package manager, a Nix implementation. Please be mindful of ongoing technical conversations in this channel. | 141 Servers |
| Sender | Message | Time |
|---|---|---|
| 23 Apr 2026 | ||
| On a re-read that’s what it says! Just hard to form a mental picture without seeing it in action tbh | 19:56:35 | |
| 25 Apr 2026 | ||
| 11:19:23 | ||
| I'm planning to migrate the nixpkgs module system eval tests from bash to nix-unit. There is also lix-unit. Question in the room: any plans to add this to nixpkgs? I would then wire up the test suite against that. Or do people have there own module system tests in lix? | 11:21:53 | |
| does nix-unit support all the supported versions of the Nix C++ API? otherwise we lose the ability to test on those versions, no? | 11:29:27 | |
| and https://github.com/adisbladis/lix-unit is archived for years unless it was moved | 11:30:20 | |
In reply to @hsjobeki:matrix.orgI’m not sure it’s a great idea. The tests are used for both cppnix/lix CI I think, and it would be quite intractable. Maybe if it could be polyfilled somehow then it would be nice yes | 11:36:44 | |
| Hm. Trying to get rid of this bash script for years now... Maybe there is a different way. | 12:14:28 | |
| 27 Apr 2026 | ||
i'm not sure why, but the repl-characterization-tests are not failing as expected in some cases.for example, if i change one of the data files (e.g. replacing "hello" with "hi" in tests/functiona/repl_characterization/data/regression_9917.nix), the test doesn't fail when it clearly should.(i'm noticing this because i'm trying to understand why tests didn't fail in cl/5491 when they clearly should have) | 11:04:40 | |
* i'm not sure why, but the repl-characterization-tests are not failing as expected in some cases.for example, if i change one of the data files (e.g. replacing "hello" with "hi" in tests/functiona/repl_characterization/data/regression_9917.nix), the test doesn't fail when it clearly should.edit: even after a clean rebuild, it just doesn't seem to pick up on the change, which is... so strange @_@ (i'm noticing this because i'm trying to understand why tests didn't fail in cl/5491 when they clearly should have) | 11:22:37 | |
| ok even changing the actual test (not just the data) still doesn't make the test fail, so i'm not sure what is even happening.
| 11:36:34 | |
| * ok even changing the actual test (not just the data) still doesn't make the test fail, so i'm not sure what is even happening.
| 11:36:53 | |
| i'm gonna try to bisect this, but i don't have a very powerful machine (and i'm kinda doing this as a side-activity while waiting for other stuff) | 11:38:15 | |
| * i'm gonna try to bisect this, but i don't have a very powerful machine (and i'm kinda doing this as a side-activity in-between two llvm builds) | 11:38:28 | |
| Poke, any opinion on https://git.lix.systems/lix-project/lix/issues/1185 ? It would be nice if this were consistent across Lix and Cppnix, we ran into this in the snix test suite. | 14:27:52 | |
| (cc @raitobezarius:matrix.org) | 14:31:25 | |
| I think Sergei Zimmerman (xokdvium) did a lot of work to improve URL handling that Lix do not have and could explain this | 14:32:17 | |
| We should probably pick this up too | 14:32:22 | |
| But I'm not caught up yet with this and we are a bit under weather, is it urgent on your side? | 14:32:36 | |
In reply to @raitobezarius:matrix.orgAgreed. It also simplifies the code in Snix, would like to see this backported. | 14:32:52 | |
| Actually, this is not in the URL code | 14:33:12 | |
In reply to @raitobezarius:matrix.orgIt's soft-blocking some test suite refactorings / migrations, which started to surface this. | 14:33:42 | |
| This is the case of error vs success case right? So this is a much softer kind of "regression" (more like a bugfix?) | 14:34:12 | |
| I will try to poke some folks, but please give us at least 1-2 weeks min to react properly to this | 14:34:59 | |
In reply to @xokdvium:matrix.orgWe didn't run some of the test suite tests yet. And now because they fail with Lix we need to distinguish between the two impls that the runner of the test suite might run them against. Or skip them entirely | 14:58:14 | |
| We can do of course, it's just I'd like to get the ball rolling, and I think it's enough of a niche case to backport and align behaviours again | 14:58:59 | |
| 16 May 2024 | ||
| 13:54:49 | ||
In reply to @lunaphied:lunaphied.meThe other thing that I could do if it helps is test things and try to find bugs. I did do some C++ work in the past, but may lack the time to do it justice here at least for about 30 days or so | 15:55:29 | |
| we are not in any rush 🙂 | 17:20:53 | |
| Would it help to also test out the existing Lix code and try to find issues/bugs etc? | 17:23:21 | |
| absolutely | 17:23:41 | |