<ekleog>
(from #nixos-dev) srhb: so the issue with setting up my hydra would be that unless I'm syncing it to be in lockstep with nixos' hydra, I'd end up building a lot of stuff in parallel to it… wouldn't I?
<ekleog>
(and syncing it to be in lockstep with nixos' hydra requires in turn that I have access to the information when all packages have finished building on hydra)
<gchristensen>
what is it you're looing for exactly?
<srhb>
ekleog: Yes, you'd still want some way of the input only when evaluation has completed for some ref
<srhb>
of BUMPING the input only...*
<ekleog>
gchristensen: basically, a way to have a binary cache that bumps as soon as all packages have been attempted to be built, ignoring tests
<srhb>
But I wouldn't care about that if I were you
<srhb>
If you have a jobset that only includes your tests, it's not like it will build all of nixpkgs
<srhb>
Just every dependency of your tests, in the worst case.
<ekleog>
hmmmm
<srhb>
So it's only terribad if glibc bumps :-)
<srhb>
But that would also be the case with your idea if glibc fails on master.
<gchristensen>
ekleog: can you wait until the tests have finished, whether or not they passd?
__monty__ has joined #nixos-chat
<ekleog>
srhb: and so I hope the user waits long enough before doing its system rebuild so that hydra has finished building the rest in the meantime?
<ekleog>
gchristensen: I can (would guess that's a negligible time difference), but I don't know how to access the information of “when” :/
<srhb>
Poll!
<srhb>
If you think it's hacky, be soothed by the fact that everything in the channel architecture works like this. :-P
<ekleog>
well, I guess I can just test for a is-ancestor when getting updates :)
<ekleog>
srhb gchristensen : thanks! :D
<andi->
ekleog: if you finish what you descibed there I would be interested on how it looks in the end.. I have been thinking about similar stuff :)
<ekleog>
andi-: tbh it's not something I have a short-term project on, I was trying to push for a nixpkgs-18.09 channel now because I knew I wouldn't get one before at least a few months / years even if everyone agreed… so the news that it's actually not required means this part of the project is now way ahead of the schedule ^^
<srhb>
Perhaps we could throw a <runcommand> at our hydra to actually ship off the JSON as soon as tested completes
<srhb>
It could be useful to more people, and that's pretty general
<srhb>
If it's new enough to have runcommand..
sir_guy_carleton has quit [Remote host closed the connection]
<ekleog>
“the JSON”? (sorry, I have literally 0 idea of how hydra works)
<andi->
ekleog: I think we srhb meant was the result JSON that you usually get when querying `latest-eval`.
<srhb>
ekleog: Hydra recently got a runcommand plugin which can execute an arbitrary script on completion (not necessarily success) of an arbitrary job. That script will get an env var which points to a json file containing information about the finished build
<srhb>
ekleog: Pushing that json file on completion of certain jobs on Hydra would allow you to poll that url for changes.
<ekleog>
andi-: wait, a result JSON? I get a redirection to an http page on `latest-eval`
<ekleog>
srhb: oh 'k, thanks :)
<andi->
ekleog: that redirect (if requested with c-t application/json) will be what the channel bump scripts use for example.
<ekleog>
oh nice, thanks! :)
<ekleog>
but then… isn't it already pushed immediately?
<gchristensen>
heh
<gchristensen>
this is getting in to the weeds a bit
<gchristensen>
the channel update scripts poll that URL with Content-Type: application/json to monitor it for advances, it then starts a process of publishing a nixexprs.tar.xz and other metadata
drakonis1 has joined #nixos-chat
drakonis1 has quit [Quit: WeeChat 2.2]
drakonis has quit [Ping timeout: 268 seconds]
drakonis_ has joined #nixos-chat
drakonis has joined #nixos-chat
drakonis_ has quit [Ping timeout: 252 seconds]
drakonis_ has joined #nixos-chat
drakonis has quit [Ping timeout: 246 seconds]
drakonis has joined #nixos-chat
drakonis_ has quit [Ping timeout: 250 seconds]
sir_guy_carleton has joined #nixos-chat
drakonis_ has joined #nixos-chat
drakonis has quit [Ping timeout: 252 seconds]
drakonis_ has quit [Ping timeout: 252 seconds]
drakonis_ has joined #nixos-chat
drakonis_ has quit [Ping timeout: 252 seconds]
drakonis_ has joined #nixos-chat
drakonis has joined #nixos-chat
drakonis_ has quit [Ping timeout: 260 seconds]
<gchristensen>
you don't really truly appreciate nixops until you don't have it