| 11 Jun 2026 |
Astreaprtcl | i am sorry to bother, but it seems the pipeline has failed with dns issues https://buildkite.com/afnix/lix/builds/1898 | 10:09:17 |
| 12 Jun 2026 |
| DontBlameMe joined the room. | 16:25:50 |
| 13 Jun 2026 |
| debtquity set a profile picture. | 03:23:23 |
| Pengo joined the room. | 08:02:46 |
| brume joined the room. | 16:22:49 |
| 17 Jun 2026 |
| Jibi joined the room. | 14:12:35 |
| 18 Jun 2026 |
Puna | would it be acceptable to raise the timeout on the functional2 testsuite to like, triple its current value (300 seconds)? my ppc64 hardware is nowhere close to completing that in time when building lixPackageSets.latest.lix in Nixpkgs
lix> 80/80 installcheck - lix:functional2 OK 712.47s 1118 subtests passed
| 13:20:36 |
raitobezarius (DECT: 7248) | Should it be sent to nixpkgs or do you need it on the HEAD builds as well? | 13:26:49 |
raitobezarius (DECT: 7248) | I'd also say that a conditional timeout based on the architecture doesn't surprise me at all | 13:27:02 |
Puna | well the machine is sadly 21 years old, so that's prolly the main reason for it taking so long… just the cheapest available ppc64 hardware | 13:28:29 |
Puna | i'm fine with w/e, would just like to avoid carrying a patch for this in my branch forever | 13:29:56 |
raitobezarius (DECT: 7248) | please send it first to nixpkgs if that's what you are using with a conditional to keep the short timeout for fast architectures and a default slow timeouts for others architectures | 13:30:19 |
raitobezarius (DECT: 7248) | put me reviewer and i will take care of it | 13:30:22 |
Puna | well, a more recent POWER machine bought from IBM (or prolly smth from raptor too) would likely be fine with the current timeout. it's not really an issue with the architecture, just with me not being made out of money to afford fancy new machines :) but can discuss that on the pull request ig | 13:34:29 |
Puna | * well, a more recent POWER machine bought from IBM (or prolly smth from raptor too) would likely be fine with the current timeout. it's not really an issue with the architecture, just with me not being made out of money to afford fancy new machines :) but can discuss that on the pull request ig edit: https://github.com/NixOS/nixpkgs/pull/532989 | 16:40:49 |
| whispers [& it/fae] changed their display name from whispers [& it/fae] to meow meow. | 18:47:00 |
| whispers [& it/fae] changed their display name from meow meow to whispers [& it/fae]. | 19:12:37 |
| 16 May 2024 |
| zrsk joined the room. | 13:54:49 |
samrose | In reply to @lunaphied:lunaphied.me I think there were a few CLs on the Gerrit but nothing being actively worked The 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 |
Qyriad | we are not in any rush 🙂 | 17:20:53 |
samrose | Would it help to also test out the existing Lix code and try to find issues/bugs etc? | 17:23:21 |
Qyriad | absolutely | 17:23:41 |
samrose |
- how do people feel about the existing test suite that comes along with nix source code or Lix?
| 17:23:48 |
Qyriad | it's pitiful | 17:24:10 |
samrose | heh | 17:24:16 |
raitobezarius (DECT: 7248) | expanding it is cool | 17:24:23 |
raitobezarius (DECT: 7248) | writing new tests for builtins which are not tested | 17:24:30 |
raitobezarius (DECT: 7248) | new test behaviors, etc. | 17:24:32 |
Qyriad | we have three flavors of test:
gtest (offer only available in libexpr and libutil) bash script virtual machine
the vast, vast majority of testing is in the "bash script" flavor and it is a mess | 17:25:01 |
samrose | I was just going to ask on the "functional" tests: do we still like using bash there? | 17:25:56 |