<ekleog>
Is there any logic in the Build ID on hydra? Like, are them monotonically increasing or whatever?
<ekleog>
(wrt. the commit version, not wrt. time of end of the build)
<ekleog>
(unrelatedly… just noticed the most recent build appears to be on the left side of the chart, I've been wrong on that for like one year of looking at it \o/)
lassulus has quit [Ping timeout: 264 seconds]
lassulus_ is now known as lassulus
<clever>
ekleog: every time an eval finishes, hydra will assign the jobs that differ from the previous eval a new sequential buildid#
<clever>
ekleog: if it differs from the previous eval, but was built before, it gets a new id, but later finishes instantly as a cached build
<clever>
and it shares the numbers across all builds
<ekleog>
clever: ok thanks! :)
<ekleog>
so it's sequential per end of eval and/or manual trigger, iiuc
<ekleog>
'k thanks! :) (though I must say I don't speak Perl yet… should really get to learn it some day)
<ekleog>
so now I think I more or less understand the basics of hydra's UI… I still can't see the reason why https://hydra.nixos.org/eval/1485074#tabs-now-fail made so many packages fail, like qtwebkit, while the two only commits compared to previous evaluation are “ruby: 2.5.2 -> 2.5.3” and “kitty: fix locating libstartup-notification-1” o.O
* ekleog
thought it was him misreading the UI and taking things against the passage of time or something like that
<clever>
ekleog: it might also be a random failure, checkout the exact rev listed under inputs and try building it locally
<ekleog>
well it looks like a syntax error from the log, so random failure sounds unlikely, but going to try :)
<ekleog>
(then, it's ike, ISTR it does have issues… if that's again the case maybe it'd be better to just disable it, and that'd actually make channels move faster?)
<clever>
ekleog: where do you see the syntax error?
<ekleog>
(also, I think maybe ike should be disabled / fixed? it appears to have been the source of every transient build failure I've heard of until now, maybe it's bad disk/ram? don't know whom to poke about this, though)
<{^_^}>
#18194 (by elasticdog, 2 years ago, open): pythonPackages.gdal broken on x86_64-darwin
<andi->
ekleog: done
<ekleog>
thanks! :)
<andi->
that reminds me of that 1-line single-build-restart change I have somewhere for hydra.
<ekleog>
(btw, there should be a list somewhere of people who can restart hydra jobs so we could just randomly pick someone, but just like for removing ike I don't know who to contact to actually make this change :/)
<andi->
Should open a PR
drakonis has joined #nixos-dev
drakonis_ has quit [Ping timeout: 252 seconds]
orivej has joined #nixos-dev
orivej has quit [Ping timeout: 245 seconds]
lopsided98 has quit [Ping timeout: 260 seconds]
lopsided98 has joined #nixos-dev
phreedom has quit [Ping timeout: 256 seconds]
phreedom has joined #nixos-dev
xeji has joined #nixos-dev
orivej has joined #nixos-dev
orivej has quit [Ping timeout: 252 seconds]
orivej has joined #nixos-dev
vcunat has joined #nixos-dev
<ekleog>
andi-: but… to where? :/
xeji has quit [Ping timeout: 252 seconds]
<andi->
andi-: hu? I meant the Hydra change for restarting a single build/job
<ekleog>
oh, sorry ^^' I just came back here without the message timing in mind and thought you were answering me to make a PR removing ike…
<andi->
ekleog: there seems to be a repo (nixos-org-hardware?) Where all machines are listed... But on the other hand there seems to be a deadlock issue which was attempted to be fixed. Not sure if the fix was ever applied there..
sir_guy_carleton has joined #nixos-dev
<ekleog>
nixos-org-hardware? can't find anything that sounds like it :/
<andi->
Will check when I am at the computer later on.. Just about to board.
<thoughtpolice>
ekleog: The nixos.org configurations are in https://github.com/NixOS/nixos-org-configurations, which contains some traces of the hardware used for the build machines, though it doesn't seem comprehensive
<thoughtpolice>
However, these don't include things like the info on the packet.net machines for nix.distributedBuildMachines (or whatever it's called), so I don't think that's complete