gchristensen changed the topic of #nixos-dev to: NixOS Development (#nixos for questions) | https://hydra.nixos.org/jobset/nixos/trunk-combined https://channels.nix.gsc.io/graph.html https://r13y.com | 18.09 release managers: vcunat,samueldr | 19.03 RMs: samueldr,sphalerite | https://logs.nix.samueldr.com/nixos-dev
janneke has quit [Ping timeout: 246 seconds]
janneke has joined #nixos-dev
page has quit [Ping timeout: 255 seconds]
page has joined #nixos-dev
drakonis_ has joined #nixos-dev
drakonis has quit [Ping timeout: 252 seconds]
drakonis has joined #nixos-dev
noonien has quit [Quit: Connection closed for inactivity]
ajs124 has left #nixos-dev [#nixos-dev]
ajs124 has joined #nixos-dev
ajs124 has left #nixos-dev [#nixos-dev]
ajs124 has joined #nixos-dev
ajs124 has left #nixos-dev [#nixos-dev]
ajs124 has joined #nixos-dev
ajs124 has left #nixos-dev [#nixos-dev]
ajs124 has joined #nixos-dev
ajs124 has left #nixos-dev [#nixos-dev]
ajs124 has joined #nixos-dev
ajs124 has left #nixos-dev [#nixos-dev]
drakonis has quit [Quit: WeeChat 2.3]
orivej has joined #nixos-dev
ajs124 has joined #nixos-dev
<Mic92> gchristensen: Yeah, but I will probably not upstream it myself. But you can give it a shot if you find the time.
Zer000 has quit [Ping timeout: 250 seconds]
<gchristensen> ok, cool
<infinisil> sphalerite: samueldr: Do you have an ETA for 19.03? :D
<sphalerite> infinisil: no >.<
<gchristensen> what can we do to help?
<gchristensen> going through 18.09 -> 19.03 tags to find important changelog entries
<globin> sphalerite, gchristensen: I'm using my company account and for hydra I just use a temp browser (chromium --user-data-dir=$(mktemp -d /tmp/chr.XXXXXX) --no-first-run --incognito)
<gchristensen> oh fancy
<globin> sphalerite: what blockers are there>
<gchristensen> I think he sorted it
<gchristensen> but would prefer a local account, instead of using a work gmail
drakonis has joined #nixos-dev
drakonis_ has quit [Ping timeout: 246 seconds]
drakonis has quit [Ping timeout: 258 seconds]
<sphalerite> yeah that's not a blocker though
<sphalerite> briefly discussed starting an RFC with fpletz regarding not requiring google accounts for hydra access yesterday, but that's for after the release :)
<infinisil> sphalerite: Why an RFC for that
<infinisil> There's no point in discussing something so non-controversial :)
<gchristensen> I think there is good value in discussing implementation details
<domenkozar> any weekly content for tomorrow? )
<fadenb> domenkozar: There was some talk on the wiki channel whether we might want to feature good articles
<srhb> Do we have graphs of queued (hydra jobs per arch) over time? I forget..
<samueldr> yes
<srhb> samueldr: Thanks!
<samueldr> Too many heap sections, nixos:release-19.03 @ ~14:38 UTC -> https://gist.github.com/samueldr/e2f6cd2fd3d295ed4352661caf752982
drakonis has joined #nixos-dev
drakonis_ has joined #nixos-dev
drakonis has quit [Ping timeout: 250 seconds]
drakonis_ has quit [Read error: Connection reset by peer]
drakonis_ has joined #nixos-dev
drakonis_ has quit [Ping timeout: 240 seconds]
<sphalerite> gchristensen: thanks, sorry, project $work occupying most of my $work time. Yeah going through the log is most of the remaining work
jtojnar has joined #nixos-dev
obadz has quit [Ping timeout: 250 seconds]
obadz has joined #nixos-dev
<sphalerite> samueldr: gchristensen: so you've both been looking at the logs?
<samueldr> (not yet)
<gchristensen> I haven't either
<gchristensen> but maybe if I were assigned a section of the logs, for example, I could help
drakonis_ has joined #nixos-dev
<sphalerite> ah ok
<sphalerite> hm
Zer000 has joined #nixos-dev
<sphalerite> samueldr: gchristensen: ssh -p1903 bar@sphalerite.org , in there emacsclient -c , C-x b revs<RET> — that should let us collaboratively go through the issues and mark them as done
<gchristensen> O.O
<gchristensen> hah!
<samueldr> what I did last year
<samueldr> was to list nixos, pkgs and lib folder separately for commits
<sphalerite> I need to go to bed now, will do some stuff on the project tomorrow morning
<sphalerite> Thanks for your help ♥
<ajs124> how is the git(v2) cache of builtin.fetchgit "pruned"/"gc"ed?
* samueldr has no emacs experience :/ how should I detach properly?
<sphalerit> C-x C-c
drakonis has joined #nixos-dev
drakonis1 has joined #nixos-dev
drakonis_ has quit [Ping timeout: 252 seconds]
drakonis has quit [Ping timeout: 258 seconds]
<ajs124> I'm asking, because mine has grown to over 40GB now
drakonis has joined #nixos-dev
drakonis1 has quit [Ping timeout: 246 seconds]
drakonis has quit [Ping timeout: 268 seconds]
<timokau[m]> What does it mean when hydra lists "hydra" as the build machine?
<gchristensen> heh
<gchristensen> hydra.nixos.org runs on `chef`
<gchristensen> it used to run on `hydra`, now, the machine named `hydra` is a build machine
<timokau[m]> Not confusing at all :D
<timokau[m]> I can't find that machine on grafana though, am I just not looking hard enough or is it not there?
<gchristensen> it may not be there, there isn't 100% coverage yet
<timokau[m]> Alright, that's a shame. Thanks anyways :)
<gchristensen> it'll happen, but we are very volunteer with lots of things :)
<timokau[m]> Of course, not complaining. Just grasping at straws anyways, probably the monitoring wouldn't have helped much either way
<gchristensen> +1
<gchristensen> what're you looking for?
<timokau[m]> Some transient failure in the sage test suite that has been coming up every once in a while
<timokau[m]> Haven't seen it locally yet and unfortunately restarted previous builds so don't know if it has always been the same machine
drakonis has joined #nixos-dev
<samueldr> seems to have failed once on ike too
<samueldr> though some were restarted, the log will show the restarted one I think
<samueldr> (follow the propagated build)
<timokau[m]> That's a different failure mode though (sage being famously frickle)
<samueldr> I didn't look closely at the failure mode :)
<timokau[m]> The distinguishing thing here are all the graph related tests failing (as seen in all the test files in `src/sage/graphs` reported at the end of the log)
orivej has quit [Ping timeout: 255 seconds]
<timokau[m]> Thanks for taking a look :)
janneke has quit [Quit: janneke quits Mes'sing]
janneke has joined #nixos-dev
<samueldr> timokau[m]: if you want to estimate what kind of hardware it runs
<samueldr> it's likely a poweredge 1250
<samueldr> 1950*
<samueldr> at best a 5300 series xeon, otherwise 5000 up to 5300 I guess :/
<timokau[m]> How do you figure that? Just from the imported hardware config?
<samueldr> yeah
<samueldr> a thick slice of assumptions on there
<timokau[m]> maxJobs 8 at least suggests that its not some crazy-high-thread-count thing
<samueldr> likely to be a 2×quad core 5300 series I guess?
<timokau[m]> Anyways getting late here, this will have to wait for another day. Thanks again!
<gchristensen> if y'all have specific Q's I can answer some =)
<samueldr> I'm thinking CPU features
<samueldr> 5300 series should be clovertown https://en.wikipedia.org/wiki/List_of_Intel_Xeon_microprocessors#%22Clovertown%22_(65_nm)
<timokau[m]> (Not complaining if I nerdsniped anyone else and the problem is solved in the morning of course ;) )
<gchristensen> specific Q's in the format of a series of commands to share, happy to run them
<samueldr> I'm a bit concerned by CPU features and how it's not handled
<samueldr> (seemingly)
<samueldr> same for the ARM arches
<timokau[m]> samueldr: True, seems like something the sandbox should handle
<samueldr> not even sure it can :/ not sure if you can reliably block access or track access to cpu features
<gchristensen> don't think it can
<samueldr> or, more to the point: I'm sure I don't know anything of use
<timokau[m]> Except through expensive virtualization of course
jtojnar has quit [Quit: jtojnar]
* samueldr boots the old core 2 duo laptop
<samueldr> gchristensen: might be interesting to see a lscpu for all machines in an inventory (with other relevant infos) to help figure out equivalent arches
<samueldr> <3 gchristensen
<{^_^}> gchristensen's karma got increased to 93
<samueldr> that's the kind of info that might help reproducing issues if cpu features are suspected
<gchristensen> <3 nixops ssh-for-each :)
<samueldr> verified: that core 2 duo machine has no CPU features that hydra wouldn't, except one specific to cpu speed stepping in laptops
* samueldr waits on it to update
<gchristensen> r13y helps with these sorts of things, too.
<samueldr> yeah, that's the one I wanted to get up and running doing those kind of things
<samueldr> otherwise I'm not using it
<gchristensen> nice
<gchristensen> please do =) (though I'll need to finish the "distributed" part of it
<samueldr> first, updating it and making it nice to use will help me just impulsively try things
drakonis has quit [Ping timeout: 250 seconds]
janneke has quit [Quit: janneke quits Mes'sing]
janneke has joined #nixos-dev