gchristensen changed the topic of #nixos-borg to: https://www.patreon.com/ofborg https://monitoring.nix.ci/dashboard/db/ofborg?refresh=10s&orgId=1&from=now-1h&to=now "I get to skip reviewing the PHP code and just wait until it is rewritten in something sane, like POSIX shell. || https://logs.nix.samueldr.com/nixos-borg
<ekleog> hmm, can anyone here attempt to `git clone https://github.com/NixOS/ofborg && cd ofborg && git checkout origin/next && nix-shell --pure && cd ofborg && cargo test`? I'm getting 10 failed tests :/
<ekleog> (well, not actually && after the nix-shell, but you got what I meant)
jtojnar_ has joined #nixos-borg
jtojnar has quit [Read error: Connection reset by peer]
<samueldr> hmmm... nix-shell --pure loads .bashrc?
jtojnar has joined #nixos-borg
<samueldr> (it's running, now that I found why `nix-shell --pure` didn't work)
<samueldr> test result: FAILED. 58 passed; 10 failed; 0 ignored; 0 measured; 0 filtered out
<samueldr> ekleog: ^
<ekleog> ok thanks, so it's not just me, just that origin/next is borked :/
jtojnar_ has quit [Ping timeout: 268 seconds]
<samueldr> am I wrong in finding it impure that `nix-shell --pure` sources .bashrc?
<samueldr> I don't remember having had the same issue with nix 1.11...
<samueldr> ... my .bashrc is made to auto-start tmux, which may or may not be a bad idea
<ekleog> I'd say you're likely right, but as nix-shell-in-nix-shell never worked it's hard to test with nix 1.11 now :/
<samueldr> and using the full path to a fallback nix 1.11?
* samueldr tries
<samueldr> > Nix database directory ‘/nix/var/nix/db’ is not writable: Permission denied
<samueldr> :/ even rebooting to a 17.09 generation isn't successful
<samueldr> > error: cannot connect to daemon at ‘/nix/var/nix/daemon-socket/socket’: Connection refused
<ekleog> that's weird, rebooting to a 17.09 generation should have a 1.11 daemon running, shouldn't it?
<samueldr> I would have hoped
<ekleog> is that what ps aux | grep nix-daemon confirms?
<ekleog> oh it's not displaying full path
<samueldr> (re-rebooting)
<samueldr> it's on a tertiary machine
<samueldr> OH
<samueldr> I thought I updated all my machines here
<samueldr> but I didn't!
<samueldr> (I had an idea before you asked tof ps aux)
<samueldr> (but didn't want to share because it felt improbable)
<samueldr> it only happens through ssh!
<samueldr> same machine, locally it works, through ssh, connection refused!
<ekleog> what?
<samueldr> though, on a(nother) 17.09 machine, through ssh there's no issue
<samueldr> now it's getting ony my nerves :/
<ekleog> oh, maybe polkit(systemd) having fun?
<samueldr> oh, even dumber, possibly
* samueldr checks
<samueldr> it's an atom computer, freshly booted, could the nix daemon simply haven't been up?
<samueldr> I'm having trouble finding proof
<samueldr> yeah, sshd was up two full minutes before nix-daemon!
<samueldr> yay! I'm just impatient
<ekleog> x)
<samueldr> (I made a diff of `env` on both sessions, and except SSH specific and X stuff, all identical)
jtojnar_ has joined #nixos-borg
jtojnar has quit [Read error: Connection reset by peer]
<samueldr> well, nix-shell 1.11 does, too, source .bashrc, something else must be causing the issue
<samueldr> oh, ah, I already had a fix, and semantics must have changed for $IN_NIX_SHELL
jtojnar_ has quit [Ping timeout: 248 seconds]
<ekleog> … ok, I don't get what hubcaps is doing, it's on gchristensen's fork but I don't get how <hubcap::issues::IssueRef>.get() can return a Result<hubcaps::Issue::Issue, hubcaps::Error>, as on docs.rs until 0.3.16 there was no `.get()`, and after 0.4.0 it returned a Future…
<gchristensen> that is my fork
<gchristensen> you should look at my fork's docs :)
<ekleog> well, your fork having been fully merged in master I hoped some version's docs would match approximately, but… do you have a docs.rs equivalent somewhere? :°
<gchristensen> `cargo doc`
<ekleog> … ok well, guess there's no way around it
<gchristensen> I just synced email for the first time all week and I have 1,500 new ...
<gchristensen> omg no its +5000
jtojnar has joined #nixos-borg
jtojnar has quit [Ping timeout: 240 seconds]
timokau[m] has quit [Ping timeout: 256 seconds]
hedning[m] has quit [Ping timeout: 240 seconds]
dywedir[m] has quit [Ping timeout: 260 seconds]
dtz has quit [Ping timeout: 255 seconds]
grahamc has quit [Ping timeout: 255 seconds]
<{^_^}> [ofborg] @Ekleog opened pull request #164 → Make ofborg able to (un)label issues and PRs → https://git.io/vpC2M
<ekleog> gchristensen: ^ not really ready yet, but as I know nothing about AMQP and have no way that I know of of testing stuff, wanting to check at least the AMQP setup looks correct to you before continuing :)
<gchristensen> oh cool
<gchristensen> I'm quite busy this week, and not at home
<gchristensen> ping me next tuesday?
<ekleog> will remember to :)
<gchristensen> thanks! I love it!
jtojnar has joined #nixos-borg
orivej has joined #nixos-borg
MichaelRaskin has quit [Remote host closed the connection]
dywedir[m] has joined #nixos-borg
hedning[m] has joined #nixos-borg
grahamc has joined #nixos-borg
dtz has joined #nixos-borg
timokau[m] has joined #nixos-borg
grahamc has quit [Ping timeout: 240 seconds]
dtz has quit [Ping timeout: 240 seconds]
hedning[m] has quit [Ping timeout: 246 seconds]
timokau[m] has quit [Ping timeout: 276 seconds]
dywedir[m] has quit [Ping timeout: 276 seconds]
jtojnar_ has joined #nixos-borg
jtojnar has quit [Quit: jtojnar]
jtojnar has joined #nixos-borg
jtojnar_ has quit [Ping timeout: 240 seconds]
jtojnar_ has joined #nixos-borg
jtojnar has quit [Read error: Connection reset by peer]
jtojnar has joined #nixos-borg
jtojnar_ has quit [Ping timeout: 276 seconds]
dywedir[m] has joined #nixos-borg
jtojnar_ has joined #nixos-borg
jtojnar has quit [Ping timeout: 256 seconds]
jtojnar_ is now known as jtojnar
grahamc has joined #nixos-borg
hedning[m] has joined #nixos-borg
dtz has joined #nixos-borg
timokau[m] has joined #nixos-borg
jtojnar has quit [Remote host closed the connection]
tilpner has quit [Quit: :wq]
jtojnar has joined #nixos-borg
tilpner has joined #nixos-borg
tilpner has quit [Ping timeout: 264 seconds]
jtojnar has quit [Quit: jtojnar]
tilpner has joined #nixos-borg
<{^_^}> [ofborg] @gilligan opened pull request #165 → Add gilligan to trusted users → https://git.io/vpWP0
andi- has quit [Ping timeout: 264 seconds]
andi- has joined #nixos-borg
<Mic92_> gchristensen: I guess this could need an update? https://nixos.wiki/wiki/Install_Nix_in_multi-user_mode_on_non-NixOS
MichaelRaskin has joined #nixos-borg
<MichaelRaskin> Booted my builder again… Wow, quite a bit of backlog for ofborg…
<LnL> is yours the only one building stuff?
<MichaelRaskin> I _hope_ not
<MichaelRaskin> I mean, I do shutdown it sometimes, and when asking for credentials I did ask if the builder that lives on a table in an apartment — and gets shut down quite often — is useful at all…
<MichaelRaskin> It _might_ be the most powerful, though.
<MichaelRaskin> 16 GiB RAM, and an i7 4770R that is often only divided among the ofborg jobs.
<LnL> gchristensen: did you do something?
<MichaelRaskin> I think he is away anyway?
<LnL> whoa, why is the dashboard fraking out my browser
<MichaelRaskin> What is the URL again?
<MichaelRaskin> I tried to remember, but I ended up with the wrong dashboard…
<LnL> oh it's the alerts
<MichaelRaskin> Oh
<LnL> your restart definitely unblocked something
<MichaelRaskin> I only remembered https://nix.ci/status
<MichaelRaskin> It wasn't really a restart — there was a clean shutdown (for reasons), and now a startup
<MichaelRaskin> !!FUN!!
<MichaelRaskin> I mean, my builder is indeed the only one
<samueldr> :/ could it be the others are online but not connected? and the owners don't know?
<LnL> don't think so, I see 3 in progress now
<MichaelRaskin> These are three threads I have spawned!
<MichaelRaskin> And yes, the fourth one is _also_ me.
<samueldr> the saviour!
<LnL> oh
<MichaelRaskin> We have not too much parallelism in Nixpkgs
<MichaelRaskin> So when I see an epic fail I spawn a lot of threads to do load-balancing
<MichaelRaskin> That's quite an epic provisioning fail…
<samueldr> does it look like the moment you would have powered off your computer?
<MichaelRaskin> It should have been ~1.5 days: I powered it off before leaving on Wednesday.
<samueldr> looks like it was
<samueldr> at a glance, ~4/25 0:00 last build for x86_64-linux, then 4/26 12:00
<MichaelRaskin> + ~ 8 hours for time difference, yeah that's it
<samueldr> I was going with "whatever the timezone is there", you said one and a half day, it looks like one and a half day :/
<LnL> doesn't look like the first time
<LnL> those don't match with your restarts right? :)
<MichaelRaskin> 12, 19, 26 sounds like my restarts…
<LnL> then there's a bug crawling around in the rabbitmq queue
<MichaelRaskin> I do not guarantee that I didn't miss something stupid on 16…
<MichaelRaskin> So maybe no bug in RabbitMQ
<LnL> my mailbox is going to be filled with build results from merged PRs now :p
<MichaelRaskin> Don't you have automation for auto-discarding ofborg notifications when necessary?
<LnL> nope
<LnL> don't know if it's even possible to write a rule that's smart enough to do that
<MichaelRaskin> What's the problem?
<MichaelRaskin> From: GrahamcOfBorg <notifications@github.com>
<LnL> I still want those, just not for things that are merged already.
<MichaelRaskin> For me it depends
<MichaelRaskin> But I am still subscribed not just to mentions
<LnL> I don't get everything but I manually subscribe to a lot of threads
<MichaelRaskin> I think I remember now what 16th was
<MichaelRaskin> So maybe all the recent troubles are my builder going away
<MichaelRaskin> Nya, all amd64 jobs now in progress
<MichaelRaskin> Wait a minute, building a stdenv will timeout for sure, right?
<infinisil> Hey gchristensen, can borg use Nix 1.11 for evaluation instead?
<infinisil> Would be useful so people don't merge Nix 2.0 only features into nix: https://github.com/NixOS/nixpkgs/pull/38804#discussion_r184517267
<infinisil> It happened many times already..
<MichaelRaskin> There is something weird: ofborg does provide shell.nix that uses nix1 by default, when I was using it people were surprised and said they expected ofborg builders would run with nix2
<infinisil> Not sure why people would say they expect Nix 2.0
<infinisil> Well I guess you can't use the new features in nixpkgs, which people want
<MichaelRaskin> LnL: can we change ofborg meta-check rules without gchristensen deploying, or is the schema built into ofborg?
<MichaelRaskin> There is a hope that Hydra will honour meta.timeout, but ofborg complains
<LnL> as in config.checkMeta?
<MichaelRaskin> I guess we want to check but with a larger schema
<LnL> that's all in nixpkgs
<LnL> AFAIK the only thing ofborg knows about that is config.checkMeta
<MichaelRaskin> Hm
jtojnar has joined #nixos-borg