| 21 Apr 2026 |
 piegames | I see | 13:11:14 |
 goldstein | offtopic, but thank you for teaching me I can just disable SHARE_HISTORY, this was annoying me immensely | 14:46:20 |
 zoë (@blokyk) | there's actually multiple mutually-exclusive settings that control zsh, each one making you go "wait, the other one didn't do that?!" :D
| 14:51:54 |
| 23 Apr 2026 |
 antifuchs | also can I just say log-format = multiline-with-logs is so nice! first time I'm customizing that log format and it is far easier to see what's going on during nix build | 17:29:53 |
| antifuchs | (the explanation in the manual is a little less clear re. the differences to bar-with-logs though. is the diff that multiline-with-logs shows the currently active tasks below the bar?) | 17:31:09 |
 kloenk | yeah essentially. sorry I'm bad with describing some things :) | 17:33:59 |
| antifuchs | 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 |
|  hsjobeki joined the room. | 11:19:23 |
| hsjobeki | 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 |
 emily | 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 |
| emily | and https://github.com/adisbladis/lix-unit is archived for years unless it was moved | 11:30:20 |
 Sergei Zimmerman (xokdvium) | In reply to @hsjobeki:matrix.org
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? I’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 |
| hsjobeki | Hm. Trying to get rid of this bash script for years now... Maybe there is a different way. | 12:14:28 |
| 27 Apr 2026 |
| zoë (@blokyk) | 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 |
| zoë (@blokyk) | * 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 |
| zoë (@blokyk) | 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.
$ sed -i 's/hello/bar/' tests/functional/repl_characterization/data/stack_vars.nix
$ sed -i 's/hello/foo/' tests/functional/repl_characterization/data/stack_vars.test
$ meson test -C build -v repl-characterization-tests
| 11:36:34 |
| zoë (@blokyk) | * 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.
$ sed -i 's/hello/bar/' tests/functional/repl_characterization/data/stack_vars.nix
$ sed -i 's/hello/foo/' tests/functional/repl_characterization/data/stack_vars.test
$ meson test -C build -v repl-characterization-tests
...
[ RUN ] ReplSessionTest.stack_vars
[ OK ] ReplSessionTest.stack_vars (67 ms)
| 11:36:53 |
| zoë (@blokyk) | 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 |
| zoë (@blokyk) | * 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 |
 flokli | 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 |
| flokli | (cc @raitobezarius:matrix.org) | 14:31:25 |
 raitobezarius (DECT: 7248) | 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 |
| raitobezarius (DECT: 7248) | We should probably pick this up too | 14:32:22 |
| raitobezarius (DECT: 7248) | 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 |
| flokli | In reply to @raitobezarius:matrix.org
We should probably pick this up too Agreed. It also simplifies the code in Snix, would like to see this backported. | 14:32:52 |
| raitobezarius (DECT: 7248) | Actually, this is not in the URL code | 14:33:12 |
| flokli | In reply to @raitobezarius:matrix.org
But I'm not caught up yet with this and we are a bit under weather, is it urgent on your side? It's soft-blocking some test suite refactorings / migrations, which started to surface this. | 14:33:42 |
| Sergei Zimmerman (xokdvium) | 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 |
| raitobezarius (DECT: 7248) | 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 |
| flokli | In reply to @xokdvium:matrix.org
This is the case of error vs success case right? So this is a much softer kind of "regression" (more like a bugfix?) We 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 |
