| 3 Aug 2025 |
 helle (just a stray cat girl) | needs discussing, but is reasonable to consider | 07:54:54 |
 K900 | Oh no logind doesn't have a C API for this | 07:56:51 |
 jade_ | no, because the build hook rejects if it's going to do a local build, so you have no idea whether a nix build is actively running | 08:39:53 |
 Linux Hackerman | so I've fixed cross-compilation (and the issue where I reported that it was broken was labelled as a release blocker). Would it make sense to add at least one cross build to CI, so it doesn't get broken by accident again? Or is that too costly? | 15:36:43 |
 raitobezarius | go ahead | 16:19:30 |
| raitobezarius | add it | 16:19:31 |
| raitobezarius | we are a bit strained on x86 but that shall change soon I suppose | 16:19:41 |
 just1602 | I was thinking about lix CI while listening to a podcast where someone from 0xide mention that a full rack has 2000 CPU core, 32TB of RAM and something like 250TB of storage. | 16:22:02 |
| just1602 | I was like, just half a rack would be enough to fix all our CI issues | 16:22:12 |
| raitobezarius | hahahahaha | 16:22:16 |
| raitobezarius | but we don't have millions of euros on our hand alas | 16:22:22 |
| just1602 | At some point, I hope they're gonna have enough client to sponsor some nice opensourc projects :D | 16:23:57 |
 aloisw | In reply to @raitobezarius:matrix.org
we are a bit strained on x86 but that shall change soon I suppose If you have enough aarch64 then I guess you could also do aarch64 -> x86_64 cross? | 16:42:09 |
| raitobezarius | we do have more aarch64 | 16:42:20 |
| raitobezarius | at least, x86 is doing more work than aarch64 | 16:42:25 |
| raitobezarius | so plausibly, this could be the job you described | 16:42:31 |
| raitobezarius | it will still generate more work for x86 which will have to calculate one more job at the nej phase | 16:42:43 |
| raitobezarius | but not a compilation job at least | 16:42:48 |
| K900 | But what if I add it to the goal loop | 16:44:29 |
| aloisw | In reply to @raitobezarius:matrix.org
it will still generate more work for x86 which will have to calculate one more job at the nej phase Evaling one Lix should be quite cheap though? | 16:48:19 |
| raitobezarius | In reply to @aloisw:julia0815.de
Evaling one Lix should be quite cheap though? Yeah, I didn't mean this as this would be much more expensive | 16:48:44 |
| raitobezarius | but cost for x86(after) > cost for x86(before) | 16:48:54 |
| raitobezarius | maybe by epsilon | 16:48:56 |
| K900 | I am fully ready to commit crimes to make this happen and Lix won't even be the worst of them | 16:49:53 |
| K900 | I am making a thing to forward logind wakelocks from WSL to Windows | 16:50:06 |
| K900 | It is going to be VERY CURSED and I don't care | 16:50:20 |
 WeetHet | raitobezarius: how do i read this?
https://buildkite.com/lix-project/lix/builds/3673/steps/canvas?sid=01986f84-2c33-4e02-9c8e-6ad9e83250c9 | 18:34:58 |
 Rutile (Commentator2.0) feel free to ping | ma27: currenlty rebasing the nix framework rewrite and now your test is failing... there is a chance the code is broken and not the framework but not 100% sure, could you take a look at it?
https://gerrit.lix.systems/c/lix/+/3333/ | 18:50:36 |
 ma27 | can you link me a ci failure, please? | 19:05:00 |
| Rutile (Commentator2.0) feel free to ping | ci currently has issues with some of the changes
assert nar_entries[0]["present"]
assert nar_entries[0]["hashPart"] == hash_part
assert nar_entries[0]["namePart"] == "test-file"
> assert nar_entries[0]["url"] == store.uploaded_nars[hash_part]["URL"]
E AssertionError: assert 'nar/14r07wnk...vxwm08idf.nar' == 'nar/snix-cas...?narsize=f128'
E
E - nar/snix-castore/00000000000000000000000000000000000000000000000000000?narsize=f128
E + nar/14r07wnk5h2bl40v1nknwkwrzh5li7z4bl02vcsqh52vxwm08idf.nar
the relevant error log(?)
| 19:15:21 |
