| 15 Jan 2023 |
void | Im recompiling chromium all the time ;( | 08:09:55 |
shawn8901 | In reply to @void68:matrix.org Im recompiling chromium all the time ;( Did you override the unwrapped package? If yes, then this is likely the reason you have to compile it. | 13:48:33 |
Amanda (she/her) | or if you'reon the small channel | 13:48:52 |
shawn8901 | Yeah true that's another likely reason :) | 13:49:37 |
shawn8901 | But if your question goes more in the area "how to build my own things on my own hydra instance" if you are on a flake you have to have the thing you want to build in the hydraJobs output | 13:51:42 |
void | just for expression to eval home.nix in a job. | 22:49:20 |
void | * just looking for expression to eval home.nix in a job. | 22:49:27 |
| 16 Jan 2023 |
| vertebralsilence changed their display name from flurie to Alexander Flurie. | 15:14:33 |
| 22 Jan 2023 |
| Mic92 left the room. | 20:53:57 |
| 24 Jan 2023 |
vcunat | Minor nit, probably easy to fix by someone who knows hydra's code base:
when showing commit hashes as e.g. "changes" in https://hydra.nixos.org/build/206632301
they're cut too short (6 chars) - and thus often they're not unique anymore in our huge nixpkgs repo. Just 7 would probably be quite good for some time for us. | 09:45:21 |
das_j | Yes | 09:45:43 |
das_j | https://github.com/NixOS/hydra/pull/1258 | 09:45:55 |
vcunat | Oh, and I thought I don't need to search because it's too simple 😄 | 09:47:55 |
das_j | In reply to @vcunat:matrix.org Oh, and I thought I don't need to search because it's too simple 😄 $ git rev-parse --short HEAD
d3aa3574382
| 10:16:04 |
das_j | looks like my git now things 11 characters are appropriate :O | 10:16:19 |
das_j | * looks like my git now thinks 11 characters are appropriate :O | 10:16:27 |
das_j | * looks like my git now thinks 11 characters are appropriate for nixpkgs :O | 10:16:40 |
vcunat | And I thought the suggestion of 12 was excessive. | 10:17:22 |
vcunat | I expect their calculation is aiming for high probability of all hashes being collision-free. I was OK with with high probability that one hash is collision-free. | 10:25:02 |
das_j | Hmmm, I think the jobsetinputalts table would be the best place for storing the proper lengths | 10:28:58 |
das_j | well better yet we should probably use a separate table and insert the length somewhere in hydra-val-jobset around line 820 | 10:36:44 |
das_j | * well better yet we should probably use a separate table and insert the length somewhere in hydra-eval-jobset around line 820 | 10:37:32 |
das_j | yep, we already have uri and can just have a mapping uri → length. Something around the lines of $ev->inputrevlengths->create({ uri => $input->{uri}, length -> length($input->{shortRev} // "seven77") }) | 10:40:30 |
das_j | * yep, we already have uri and can just have a mapping uri → length. Something around the lines of if ($input->{shortRev}) $ev->inputrevlengths->create({ uri => $input->{uri}, length -> length($input->{shortRev}) }) | 10:41:01 |
das_j | * yep, we already have uri and can just have a mapping uri → length. Something around the lines of if ($input->{shortRev}) $ev->inputrevlengths->create({ uri => $input->{uri}, length => length($input->{shortRev}) }) | 10:41:14 |
| 31 Jan 2023 |
| @austreelis:the-apothecary.club joined the room. | 13:02:14 |
| 1 Feb 2023 |
wucke13 | Why would hydra report "Unsupported system type" for a job that is for aarch64-linux despite having ssh://localhost (x86_64-linux, i686-linux, aarch64-linux, wasm32-wasi) in the machine status? | 15:52:53 |
@grahamc:nixos.org | you'll need to nix show-derivation on the derivation | 15:55:24 |
@grahamc:nixos.org | there might be requiredFeatures that your localhost doesn't support on that architecture | 15:55:34 |
wucke13 | The corresponding reproduce locally works on the machine hosting hydra. I'm 100% sure that this machine is actually capable of building said derivation | 15:57:47 |