!zghijEASpYQWYFzriI:nixos.org

Hydra

378 Members
110 Servers

You have reached the beginning of time (for this room).


SenderMessageTime
15 Jan 2023
@void68:matrix.orgvoid * just looking for expression to eval home.nix in a job.22:49:27
16 Jan 2023
@vertebralsilence:matrix.orgAlexander Flurie changed their display name from flurie to Alexander Flurie.15:14:33
22 Jan 2023
@joerg:thalheim.ioMic92 left the room.20:53:57
24 Jan 2023
@vcunat:matrix.orgvcunatMinor 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
@janne.hess:helsinki-systems.dedas_jYes09:45:43
@janne.hess:helsinki-systems.dedas_jhttps://github.com/NixOS/hydra/pull/125809:45:55
@vcunat:matrix.orgvcunatOh, and I thought I don't need to search because it's too simple 😄09:47:55
@janne.hess:helsinki-systems.dedas_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
@janne.hess:helsinki-systems.dedas_jlooks like my git now things 11 characters are appropriate :O10:16:19
@janne.hess:helsinki-systems.dedas_j * looks like my git now thinks 11 characters are appropriate :O10:16:27
@janne.hess:helsinki-systems.dedas_j * looks like my git now thinks 11 characters are appropriate for nixpkgs :O10:16:40
@vcunat:matrix.orgvcunatAnd I thought the suggestion of 12 was excessive.10:17:22
@vcunat:matrix.orgvcunat 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
@janne.hess:helsinki-systems.dedas_jHmmm, I think the jobsetinputalts table would be the best place for storing the proper lengths10:28:58
@janne.hess:helsinki-systems.dedas_jwell better yet we should probably use a separate table and insert the length somewhere in hydra-val-jobset around line 82010:36:44
@janne.hess:helsinki-systems.dedas_j * well better yet we should probably use a separate table and insert the length somewhere in hydra-eval-jobset around line 82010:37:32
@janne.hess:helsinki-systems.dedas_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
@janne.hess:helsinki-systems.dedas_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
@janne.hess:helsinki-systems.dedas_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@austreelis:the-apothecary.club joined the room.13:02:14
1 Feb 2023
@wucke13:matrix.orgwucke13 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

Show newer messages


Back to Room ListRoom Version: 6