| 10 Jan 2024 |
|  philipp changed their display name from philipp to test. | 13:48:33 |
| philipp changed their display name from test to philipp. | 13:49:59 |
| 11 Jan 2024 |
 pbsds | ofborg doesn't seem to request reviews from package maintainers, is this a known issue? | 01:06:55 |
 Lily Foster | In reply to @pederbs:pvv.ntnu.no
ofborg doesn't seem to request reviews from package maintainers, is this a known issue? link to pr with issue? | 01:20:56 |
| pbsds | I seem to be mistaken | 01:25:35 |
 ElvishJerricco | ofborg failed to build a test for a PR for a very strange reason. Is this something to worry about? https://logs.ofborg.org/?key=nixos/nixpkgs.280296&attempt_id=9716e851-de93-4b2a-a937-9fbf9acc4eb8 | 16:13:47 |
| Lily Foster | In reply to @elvishjerricco:matrix.org
ofborg failed to build a test for a PR for a very strange reason. Is this something to worry about? https://logs.ofborg.org/?key=nixos/nixpkgs.280296&attempt_id=9716e851-de93-4b2a-a937-9fbf9acc4eb8 the no space left bit? | 16:14:28 |
| ElvishJerricco | mainly that, but also the fact that it feels a need to build a kernel for a change like this: https://github.com/NixOS/nixpkgs/pull/280296/files | 16:15:07 |
| Lily Foster | In reply to @elvishjerricco:matrix.org
mainly that, but also the fact that it feels a need to build a kernel for a change like this: https://github.com/NixOS/nixpkgs/pull/280296/files it may not be cached on master rn 🤷🏻♀️ | 16:15:50 |
| Lily Foster | it always rebases on master and there's sometimes rebuilds of dependencies on master | 16:16:08 |
| Lily Foster | * it always applies patch against master and there's sometimes rebuilds of dependencies on master | 16:16:19 |
| ElvishJerricco | so I guess I just asked it to build too much at once and it ran out of space in /tmp? | 16:16:29 |
| ElvishJerricco | looks like kernels are not currently cached on master, and it was trying to build two of them at once to run the zfs tests | 16:18:36 |
| Lily Foster | In reply to @elvishjerricco:matrix.org
so I guess I just asked it to build too much at once and it ran out of space in /tmp? well there were kernel releases yesterday and those get merged straight to master, so i can believe that there would be kernel rebuilds on master right now and that ofborg ran out of space trying to build those so it could build the actual test | 16:18:54 |
| ElvishJerricco | I guess I'll build the tests myself then | 16:19:33 |
 ris_ | could ofborg be failing on https://github.com/NixOS/nixpkgs/pull/274089 because because it's trying to evaluate the packages in (the new) pkgsExtraHardening? | 20:09:55 |
| ris_ | * could ofborg be failing on https://github.com/NixOS/nixpkgs/pull/274089 because because it's trying to evaluate the packages in (the new) pkgsExtraHardening? | 20:10:12 |
| ris_ | * could ofborg be failing on https://github.com/NixOS/nixpkgs/pull/274089 because it's trying to evaluate the packages in (the new) pkgsExtraHardening? | 20:10:22 |
 cole-h | I doubt it. The eval failure is because the staging commit your PR is built off of was busted. If you rebase, it should work (or at least get further):
error: evaluation aborted with the following error message: 'lib.customisation.callPackageWith: Function called without required argument "filemagic" at /var/lib/ofborg/checkout/repo/38dca4e3aa6bca43ea96d2fcc04e8229/mr-est/ofborg-evaluator-1/pkgs/development/python-modules/jira/default.nix:5'
| 20:11:28 |
| Lily Foster | In reply to @r_i_s:matrix.org
could ofborg be failing on https://github.com/NixOS/nixpkgs/pull/274089 because because it's trying to evaluate the packages in (the new) pkgsExtraHardening? possibly. on a quick glance on mobile i see the ofborg-eval failure link which shows eval output says this though: Function called without required argument "filemagic"
| 20:11:36 |
| Lily Foster | yeah what cole said (i typed too slow 😅l | 20:11:57 |
| Lily Foster | * yeah what cole said (i typed too slow 😅) | 20:12:00 |
| Lily Foster | In reply to @cole-h:matrix.org
I doubt it. The eval failure is because the staging commit your PR is built off of was busted. If you rebase, it should work (or at least get further):
error: evaluation aborted with the following error message: 'lib.customisation.callPackageWith: Function called without required argument "filemagic" at /var/lib/ofborg/checkout/repo/38dca4e3aa6bca43ea96d2fcc04e8229/mr-est/ofborg-evaluator-1/pkgs/development/python-modules/jira/default.nix:5'
i mean it merged onto base branch before doing evals, so staging must have been busted at that anyway? they should just need to retrigger eval rather than rebasing | 20:12:58 |
| Lily Foster | * i mean it merges onto base branch before doing evals, so staging must have been busted at that anyway? they should just need to retrigger eval rather than rebasing | 20:13:04 |
| Lily Foster | * i mean it merges onto base branch before doing evals, so staging must have been busted at that time anyway? they should just need to retrigger eval rather than rebasing | 20:13:11 |
| 15 Jan 2024 |
 @adam:robins.wtf | how can we speed up eval and aarch64-darwin builders? can we throw money at these problems? | 13:45:02 |
| Lily Foster | In reply to @adam:robins.wtf
how can we speed up eval and aarch64-darwin builders? can we throw money at these problems? money can to an extent probably be thrown at the problem. really our eval shouldn't be so expensive, but if we had the money, we could still theoretically just get more evaluators/x86_64-linux builders (they are colocated) and more aarch64-darwin builders for short-term and have it be better (but our eval compute cost has been going up a lot the last year or so, and it's not helped by nix performance regressing in both eval time and memory pretty much every release iirc...) | 13:56:53 |
| @adam:robins.wtf | honestly i think the aarch64-darwin builders is the bigger problem. | 13:58:04 |
| @adam:robins.wtf | 12+ hours just to get time on an aarch64-darwin builder is absurd and can only hurt the support of this platform as people will merge without waiting | 14:00:00 |
| @adam:robins.wtf | especially given that x86_64-darwin, a dying platform, is competing in a much more reasonable amount of time | 14:01:21 |
