sphalerite changed the topic of #nixos-dev to: NixOS Development (#nixos for questions) | NixOS stable: 20.03 ✨ | 20.09 ZHF: https://discourse.nixos.org/t/nixos-20-09-zero-hydra-failures/8928 | https://hydra.nixos.org/jobset/nixos/trunk-combined https://channels.nix.gsc.io/graph.html | https://r13y.com | 20.03 RMs: worldofpeace, disasm; 20.09: worldofpeace, jonringer | https://logs.nix.samueldr.com/nixos-dev
justanotheruser has joined #nixos-dev
leungbk has quit [Remote host closed the connection]
<worldofpeace> samueldr: Are you familiar with the support details we have for aarch64? the failed builds I see at https://hydra.nixos.org/jobset/nixos/release-20.09-aarch64 are much much worse than last release https://hydra.nixos.org/jobset/nixos/release-20.03-aarch64, and I'm wondering how much should be reasonably fixed
<worldofpeace> I haven't really looked into it, so it could just be a timeout high up in the chain (could then be an aarch64 infra issue)
<samueldr> there's a lot of timing out around lately for reasons I want to investigate, I have asked but probably due to timezone differences no one took the bait into helping me look into a solution
<samueldr> the reports thing script I made could help to see if there is a bottleneck in failures
<samueldr> something that's making a lot of the builds fail as they are dependent
<samueldr> ~6713 are "Dependency failed"
<worldofpeace> oooh, I think I recall seeing you in here wondering about that.
<samueldr> 7 timed out
<samueldr> 664 simply "Failed"
<samueldr> how'd I check that?
<samueldr> curl'd the page source for the fully expanded list, and grepped for title="Failed" and such
<samueldr> extremely lo-fi
<worldofpeace> <samueldr "extremely lo-fi"> effective tho
<samueldr> that's basically what the reports thing does
<worldofpeace> samueldr: if we can't figure out what to do in #nixos-dev be sure to come to the go/no-go so we can "raise a stink" if needed.
<samueldr> I don't think it's "that" issue though
<samueldr> anyone ran my reports script recently?
<samueldr> hm, it'd have to be on _that_ jobset though
<worldofpeace> samueldr: jonringer has a beeeeffyy machine and I told him about this. I can ask if he can do it on an eval of that jobset
<samueldr> heh, it's not even requiring a beefy machine :) it's more about time to let it go through the builds (the first time)
<samueldr> it all relies on hydra serving us pages at an acceptable speed
<hexa-> and not doing too many jobs in parallel, even though the arm machines have lots of cores afair
<worldofpeace> <samueldr "it all relies on hydra serving u"> right, I believe that was the issue I reported to your repo last time (had to tweak the curl command in the end so it could work)
<samueldr> hm?
<worldofpeace> I don't think we documented it in https://github.com/samueldr/nix-review-tools/issues/6
<{^_^}> samueldr/nix-review-tools#6 (by worldofpeace, 31 weeks ago, open): fetch.rb:31:in `read': No such file or directory
<worldofpeace> (or maybe I'm misremembering, it's all a blur at this point)
<samueldr> ah, no, not really that, that was only when it failed
<samueldr> (looks like I fixed it)
<samueldr> what I was saying is that since it will have to go through... thousands of requests to hydra, it'll take a while :)
<samueldr> Y'ALL, DON'T GET SCARED, it does them serially
<samueldr> and caches them so when/if you restart it doesn't re-do any of those it already did, and if you run on multiple evals it completes with the new stuff
greizgh_ has joined #nixos-dev
alexarice[m] has quit [*.net *.split]
worldofpeace has quit [*.net *.split]
bennofs[m] has quit [*.net *.split]
arcnmx has quit [*.net *.split]
Ox4A6F has quit [*.net *.split]
bbigras has quit [*.net *.split]
mkg20001 has quit [*.net *.split]
greizgh has quit [*.net *.split]
fadenb has quit [*.net *.split]
stew has quit [*.net *.split]
thoughtpolice has quit [Ping timeout: 246 seconds]
thoughtpolice has joined #nixos-dev
ris has quit [Ping timeout: 264 seconds]
justanotheruser has quit [Ping timeout: 272 seconds]
__red__ has quit [Remote host closed the connection]
evanjs has quit [Read error: Connection reset by peer]
evanjs has joined #nixos-dev
evanjs has quit [Read error: Connection reset by peer]
evanjs has joined #nixos-dev
<ghuntley> q: i've started running master @ https://github.com/nixos/nixpkgs for my development workstation nix_packages.
<ghuntley> Good idea or bad idea?
<ghuntley> Or would you recommend using https://github.com/nixos/nixpkgs-channels
<ghuntley> I guess the question really is, why not use master@nixpkgs over nixpkgs-channels if one is getting their hands dirty with nix internals.
<ghuntley> or is it a case of nixpkgs-channels means there's a hydra cache available?
<samueldr> ghuntley: master could have a commit that renders the workstation unusable
<samueldr> as in, not bootable
<samueldr> not "ah, previous generation will work fine" unbootable, but could also wipe your bootloader (though, that's a bit far fetched)
<samueldr> you really should follow the `nixos-unstable` branch, on the NixOS repo (nixpkgs-channel is semi-deprecated, the branches are on the NixOS repo now too)
<ghuntley> thx sam. I didn't know nixpkgs-channel was semi deprecated. I'll switch over to nixkgs:nixos-unstable
<ghuntley> could we maybe get the note about deprecation added to the README at https://github.com/nixos/nixpkgs-channels and/or the description. Specifically with steps to mitigate.
<samueldr> I said half-deprecated, but there's no official word AFAIK
<samueldr> it's more that all the features are now active on the main repo, and that's how (IIRC) flakes get channel info by default
evanjs has quit [Read error: Connection reset by peer]
justanotheruser has joined #nixos-dev
evanjs has joined #nixos-dev
<ghuntley> does systemd have a way to run a command, when another systemd unit is invoked?
<ghuntley> use case: allow folks to specify a script to be invoked (ie clear gpg keys) when the systemd service is run
<ghuntley> question: is adding `extraCommands` the right thing or would you go the approach of a dependent systemd trigger (if such a thing exists)
rajivr has joined #nixos-dev
orivej has quit [Ping timeout: 265 seconds]
<ghuntley> in the meantime: yeet - https://github.com/NixOS/nixpkgs/pull/98914/files
justanotheruser has quit [Ping timeout: 272 seconds]
<ashkitten> ghuntley: is bindsTo the thing you want?
justanotheruser has joined #nixos-dev
<ghuntley> thx ashkitten! Yes indeed, either `bindsTo` or `Wants`. Cool thank-you.
<lovesegfault> Wrote my first NixOS module today, review appreciated :)
<{^_^}> #98917 (by lovesegfault, 5 minutes ago, open): klipper: init at 0.8.0
<lovesegfault> Hmm, does Nix have a toINI?
sphalerite has quit [Quit: WeeChat 2.6]
sphalerite has joined #nixos-dev
cole-h has quit [Quit: Goodbye]
justanotheruser has quit [Ping timeout: 240 seconds]
cransom has quit [Ping timeout: 258 seconds]
cransom has joined #nixos-dev
stew has joined #nixos-dev
bennofs[m] has joined #nixos-dev
mkg20001 has joined #nixos-dev
fadenb has joined #nixos-dev
bbigras has joined #nixos-dev
worldofpeace has joined #nixos-dev
Ox4A6F has joined #nixos-dev
arcnmx has joined #nixos-dev
alexarice[m] has joined #nixos-dev
orivej has joined #nixos-dev
mdlayher has quit [Read error: Connection reset by peer]
mdlayher has joined #nixos-dev
claudiii has quit [Read error: Connection reset by peer]
emilazy has quit [Read error: Connection reset by peer]
claudiii has joined #nixos-dev
emilazy has joined #nixos-dev
aristid has quit [Ping timeout: 260 seconds]
aristid has joined #nixos-dev
vdemeester has quit [Ping timeout: 256 seconds]
vdemeester has joined #nixos-dev
davidtwco has quit [Ping timeout: 272 seconds]
jared-w has quit [Ping timeout: 272 seconds]
davidtwco has joined #nixos-dev
jared-w has joined #nixos-dev
raboof has quit [Ping timeout: 256 seconds]
raboof has joined #nixos-dev
ehmry has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
ehmry has joined #nixos-dev
ris has joined #nixos-dev
__monty__ has joined #nixos-dev
orivej has quit [Ping timeout: 240 seconds]
tilpner_ has joined #nixos-dev
tilpner has quit [Ping timeout: 258 seconds]
tilpner_ is now known as tilpner
orivej has joined #nixos-dev
<worldofpeace> hey, https://discourse.nixos.org/t/go-no-go-meeting-nixos-20-09-nightingale/9169 - samueldr LnL infinisil domenkozar garbas flokli Mic92 ma27 aaron (other people aren't in this channel)
<aanderse> [worldofpeace](https://matrix.to/#/@worldofpeace:matrix.org) <3
<worldofpeace> And Eelco isn't on vacation anymore is he?
<worldofpeace> aaron: ✨ 💖
<aanderse> oh no... never click that link from mobile :S
<worldofpeace> aaron: discourse or is the when2meet not mobile friendly?
<aanderse> when2meet
<aanderse> no problem though, switched to desktop and all good
<worldofpeace> huh, maybe I should find a better tool. framadate is like the most painful thing to use, and when2meet is basically as "close" to a doodle without being doodle.
<ryantm> oops
<ryantm> (Note to self: don't compose messages in chat inputs)
<ryantm> Here's my idea to fix the nodePackages merge conflict hell:
<ryantm> 2. Make script that makes it easy for node maintainers to list a bunch of PRs, drop all their node-packages.nix changes, and then regenerate node-packages.nix on top of that, and make a PR.
<ryantm> 1. make node maintainer team, add code owners for node-packages.nix
<qyliss> ryantm++
<{^_^}> ryantm's karma got increased to 18
nschoe has joined #nixos-dev
<infinisil> ryantm: I think we should have CI run generate.sh on a weekly basis (and when a PR that changes node-packages.json is merged)
<infinisil> So that people only need to PR the node-packages.json update
<qyliss> I think that what ryantm is suggesting would also mean people only need to PR node-packages.json
<qyliss> I'd be a bit nervous about CI having push access
<ryantm> Yeah, they wouldn't need to PR node-packages.nix, but if they did we'd have a way to ignore it.
<ryantm> Maybe we could make a CI action that tells people they are wrong to be changing node-packages.nix?
<ryantm> There's already so many CI actions, I'm not sure people would notice.
<MichaelRaskin> ryantm: I think the total changes to red, though?
<infinisil> a github action using that should indicate failure within a couple seconds I'd expect
<worldofpeace> yeah, we use github actions in nixos-homepage to update flake and whatnot. infinisil is right in that actions can make it *really* simple
cole-h has joined #nixos-dev
<worldofpeace> wondering if anyone has anything to add for proofreading the release note at #98333
<{^_^}> https://github.com/NixOS/nixpkgs/pull/98333 (by Ma27, 6 days ago, open): nextcloud: 19.0.1 -> 19.0.3, deprecate/remove older versions
<worldofpeace> (maybe cole-h ^)
* cole-h looks
<cole-h> worldofpeace: Mind meld -- those are all things I would have pointed out :)
<cole-h> worldofpeace: However, s/timeline/lifetime/ for your first comment
<worldofpeace> cole-h: I'm noticing I'm really find of terms like "end of life" and "lifetime" when we're talking about software. I've kept them atm though
<cole-h> find -> fond? ;)
<worldofpeace> I almost
<worldofpeace> I almost was proficient at english
<worldofpeace> sooo close. yeah fond :D
<cole-h> `timeline` just sounds weird in that context, IMO, especially as the only timeline we really have is "release 20.09 eventually" (and AFAIK nothing concrete/explicit about when we stop supporting version xx.xx)
<worldofpeace> From all the rm's I've talked to its a month after the new stable release. it might be in the manual. so like 20.09 is released 20.03 is EOL in a month after that
<cole-h> Then I stand corrected. But lifetime still sounds better in that context, because it's acknowledging that 20.09's life will come to an end eventually (whereas I perceive a timeline as infinitely continuing, with marked events along it)
<cole-h> Once your suggestions are heeded, those notes should be g2g :D
<worldofpeace> awesome 👍️
red[evilred] has joined #nixos-dev
bridge[evilred] has joined #nixos-dev
rajivr has quit [Quit: Connection closed for inactivity]
kloenk has joined #nixos-dev
flokli has quit [Ping timeout: 244 seconds]
flokli has joined #nixos-dev
abathur has joined #nixos-dev
tazjin has quit [Remote host closed the connection]
tazjin has joined #nixos-dev
red[evilred] has quit [Quit: Idle timeout reached: 10800s]
nschoe has quit [Ping timeout: 272 seconds]
MichaelRaskin has quit [Quit: MichaelRaskin]
cptchaos83 has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
cptchaos83 has joined #nixos-dev
leungbk has joined #nixos-dev
__monty__ has quit [Quit: leaving]
cptchaos83 has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
cptchaos83 has joined #nixos-dev
leungbk has quit [Quit: ERC (IRC client for Emacs 28.0.50)]
tilpner has quit [Remote host closed the connection]
tilpner has joined #nixos-dev
tilpner has quit [Remote host closed the connection]
zimbatm has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
zimbatm has joined #nixos-dev
bridge[evilred] has quit [Remote host closed the connection]
jonringer has joined #nixos-dev
ehmry has quit [Ping timeout: 272 seconds]
ehmry has joined #nixos-dev