Synthetica has quit [Quit: Connection closed for inactivity]
justanotheruser has quit [Ping timeout: 246 seconds]
asymmetric has joined #nixos-dev
pie_ has quit [Ping timeout: 258 seconds]
<gchristensen>
worldofpeace++ for the staging fix
<{^_^}>
worldofpeace's karma got increased to 18
<worldofpeace>
thx gc
<worldofpeace>
gchristensen:
justanotheruser has joined #nixos-dev
<worldofpeace>
If i notice eval is broken i always try to fix it
<gchristensen>
:) I used to highlight on "gc" / "GC" until I came here and nix's gc got me pinged a lot
<gchristensen>
that is really helpful. is there something I / ofborg could do to make it easier for you?
<samueldr>
I'm removing the 18.09 jobs in my hydra dashboard, the end of an era
<gchristensen>
RIP in peace, 18.09
<worldofpeace>
gchristensen: currently I notice a pr failed eval. and that could be for lots of reasons
<worldofpeace>
gchristensen: and then after looking at the log i have to determine if it's something wrong with nixpkgs currently or the pr
justanotheruser has quit [Ping timeout: 246 seconds]
<gchristensen>
have you noticed the error message indicates it is the branc not the PR?
<worldofpeace>
No I work to fast to read gchristensen :)
<gchristensen>
this is the error that'll show up if the branch is broken: "The branch this PR will merge in to does not evaluate, and so this PR cannot be checked."
<gchristensen>
this is what shows up if the PR broke it: This PR breaks listing of package outputs after merging.
<worldofpeace>
Just looking at that particular pr and noticing that detail now
<gchristensen>
I suppose I could make that clearer then :)
<gchristensen>
maybe move it to the Checks tab, and give it a bit of text describing more in depth
<gchristensen>
would that help?
<gchristensen>
you know, I could just make the headline "staging is broken" and then sub-header "so this PR can't be checked"
<worldofpeace>
Was just going to say that.
<gchristensen>
=)
<worldofpeace>
Though the checks tab has no info if that happens
<gchristensen>
yeah
<gchristensen>
it could, though! :)
<worldofpeace>
Yeah that would help. I haven't even noticed that detail and was wasting a bit of time
<gchristensen>
cool
<worldofpeace>
Is there a nixpkgs current branch like eval status page?
<gchristensen>
I have a PR almost ready to merge which moves some of the info to the Checks page
<gchristensen>
I'll finish it off, and move the rest
<gchristensen>
hmm
<gchristensen>
I don't think so, but ofborg could publish one probably
<samueldr>
staging isn't eval'd on hydra, right? (nixpkgs:staging isn't)
<worldofpeace>
yeah and that would be the intuitive place to get that info
<worldofpeace>
hmm, all over the place idea. ofborg could comment on commits addressing the author that it broke eval and inline the log. only useful if they manually pushed it though.
<gchristensen>
yea
<gchristensen>
in other words, check each commit?
<clever>
gchristensen: that reminds me of something i saw at a google talk when i was at ase2017
<gchristensen>
or rather, each push
<clever>
gchristensen: to save CI time, the CI system will basically skip commits, and run whatever the branch is at when CI returns to idle, and if the state of any test changes, it will auto-bisect, to find out when it broke
<gchristensen>
oh cool!
<clever>
it also has things nix already has, like a complex rule system to figure out if tests actually need to re-run
<clever>
pure derivations ftw :P
<gchristensen>
:D
<clever>
but they also have other insanity
<clever>
the entire IDE lives in the browser
<clever>
and can re-run CI on-the-fly, after every save
<gchristensen>
o.o
<gchristensen>
ok, off to bed
<clever>
i'm not entirely sure how they get good perf out of that, it may be impure, like nix-shell + make check
<gchristensen>
thanks for the thoughts, worldofpeace + clever
<worldofpeace>
gchristensen: thanks for continued curiosity
<gchristensen>
:) I really, really like getting tools to people
<worldofpeace>
that and playfullness drives proactive change
<worldofpeace>
lol "gchristensen - getting the tools to the people"