!zghijEASpYQWYFzriI:nixos.org

Hydra

315 Members
94 Servers

Load older messages


SenderMessageTime
21 Sep 2024
@luna-null:matrix.orgAutumn joined the room.05:45:40
@sternenseemann:systemli.orgsterni does hydra display anywhere if a job failed due to disallowedReferences or similar? 10:41:45
23 Sep 2024
@elikoga:matrix.orgelikoga joined the room.15:30:42
@connorbaker:matrix.orgconnor (he/him) (UTC-7) changed their display name from connor (he/him) (UTC-5) to connor (he/him) (UTC-7).17:57:43
24 Sep 2024
@asymmetric:matrix.dapp.org.ukasymmetric joined the room.14:42:55
@asymmetric:matrix.dapp.org.ukasymmetric

is there a way to subscribe to hydra build failures for a specific package?

if not, is there a stable way to go attr_path -> build log? as in: i am interested in fetching the latest x86_64 build of package foo in the jobset nixos:release-24.05, is there a stable url i can periodically check for that?

14:47:57
@asymmetric:matrix.dapp.org.ukasymmetricah i guess this would answer my 2nd question: https://hydra.nixos.org/job/nixpkgs/staging-next-24.05/rippled.x86_64-linux15:14:09
@asymmetric:matrix.dapp.org.ukasymmetric why is the job (chosen at random) not present in the nixos/release-24.05 jobset? https://hydra.nixos.org/job/nixos/release-24.05/rippled.x86_64-linux 15:15:34
@asymmetric:matrix.dapp.org.ukasymmetrici'm not sure i understand the text on the page: was it removed by hand? or if it had an error, why isn't the error shown?15:16:08
@k900:0upti.meK900https://hydra.nixos.org/job/nixos/release-24.05/nixpkgs.rippled.x86_64-linux15:17:59
@k900:0upti.meK900Wrong job name15:18:01
@k900:0upti.meK900The nixpkgs jobsets only build packages, nixos jobsets build packages and nixos tests, so packages get an extra nixpkgs. namespace15:18:19
@nikolay:matrix.orgNikolay Kolev changed their profile picture.22:27:29
@ckie:ckie.devmei 🌒& changed their profile picture.23:20:39
@0lach:matrix.orgLach joined the room.23:39:00
25 Sep 2024
@luna-null:matrix.orgAutumn changed their display name from luna-null to Autumn.06:39:21
@asymmetric:matrix.dapp.org.ukasymmetricis there an API endpoint for something like https://hydra.nixos.org/job/nixos/release-24.05/nixpkgs.rippled.x86_64-linux i couldn't find it in the API docs so i guess not..?12:40:24
@asymmetric:matrix.dapp.org.ukasymmetricbasically an endpoint for a job12:40:39
@k900:0upti.meK900Don't think so 12:49:35
@rick:matrix.ciphernetics.nlMindavihttps://github.com/Mindavi/nixpkgs-mark-broken/blob/77cb016ea6ae570ec4bb861cd3f00f82e69b200f/nixpkgs-broken.py#L1413:14:35
@rick:matrix.ciphernetics.nlMindaviI think there's something13:14:44
@rick:matrix.ciphernetics.nlMindaviBut maybe not exactly what you'd like13:15:20
@k900:0upti.meK900Yeah that's by job ID13:15:34
@k900:0upti.meK900Which is the number13:15:37
@rick:matrix.ciphernetics.nlMindavi#💡 the hydra endpoint /{project-id}/{jobset-id}/{job-id}/latest (as documented here: https://github.com/NixOS/hydra/issues/1036) will return the latest _working_ build for a job! This makes it very easy to see how long a job has been broken already.13:15:41
@k900:0upti.meK900I think13:15:51
@rick:matrix.ciphernetics.nlMindaviI think so, yeah13:16:59
@rick:matrix.ciphernetics.nlMindaviI'm at least aware there are some gaps where you'd expect endpoints so it's likely the one you want is missing 13:17:53
@rick:matrix.ciphernetics.nlMindaviI ran into that too while building that script 13:17:59
@rick:matrix.ciphernetics.nlMindaviStill hoping for someone adding those endpoints, but I presume it'll be rewritten before those are added 😅. I looked at the perl but already didn't understand the existing endpoints, let alone adding some13:21:45

Show newer messages


Back to Room ListRoom Version: 6