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
orivej has joined #nixos-borg
MichaelRaskin has quit [Quit: MichaelRaskin]
<LnL> NinjaTrappeur: me hinting at using ofborg for the nixos test wasn't a joke btw :)
<LnL> but have you looked at the different travis builders available?
<LnL> maybe there's some other kind where virtualisation works properly
<NinjaTrappeur> LnL: You're right, I somehow forgot this idea in the process :)
<NinjaTrappeur> LnL: It would require to setup ofborg on this git repo though. Is it a lot of work?
<LnL> not sure if the code assumes NixOS/nixpkgs in some places
<LnL> but other then that just configuring webhooks I think
<NinjaTrappeur> Ah, sounds good!
<LnL> we don't need to deploy a separate instance
<NinjaTrappeur> As for the builder, a lot of people are actually using qemu in travis to simulate exotic hardware (PPC, RISCV, ...) using the standart builder. I come to suspect the erlang-vm to do some weird stuff while in a OpenVz->Qemu stack
<NinjaTrappeur> Thing is you don't have any ssh access and I can't reproduce this locally. It's pretty hard to troubleshoot
<LnL> yeah
<LnL> I'd take a look at the test command to see what it would take to make it less nixpkgs dependent
<NinjaTrappeur> True, we could use travis's way to setup the services. I kind of liked nixos-test as it was possible to run these tests locally without any setup.
<LnL> I mean the ofborg test command for nixos tests, but that could also work
<NinjaTrappeur> By ofborg test, you mean test that using the buider? I think it's doable as it is, I just depend of nixpkgs for this tests and if I'm not mistaken, ofborg's builders alway have a nixpkgs copy right?
<NinjaTrappeur> (this test is just a nix derivation actually)
<NinjaTrappeur> Ok, I see the problem
<LnL> build and test are different because test requires kvm and only works on linux
<LnL> so the logic for what builders to use is a bit different
<LnL> what I mean is that it might do something like nix-build /checkout/nixos -A tests.$test is a hardcoded way
<NinjaTrappeur> I'm confused >< When you say "test", are you talking to another builder than this one: https://github.com/NixOS/ofborg/blob/released/ofborg/src/tasks/build.rs#L290 ?
jtojnar has joined #nixos-borg
jtojnar has quit [Quit: jtojnar]
jtojnar has joined #nixos-borg
jtojnar has quit [Remote host closed the connection]
jtojnar has joined #nixos-borg
jtojnar has quit [Remote host closed the connection]
orivej has quit [Ping timeout: 256 seconds]
jtojnar has joined #nixos-borg
<NinjaTrappeur> Ok, I give up the CI magic for now, I think it is ready to be reviewed as a "local-only" test :) I'll probably get back to it in a few weeks. Thanks for the help LnL!
<LnL> it's useful either way
<LnL> and "local-only" using nix just means that we could use hydra
<{^_^}> [ofborg] @primeos opened pull request #180 → Add myself (primeos) to the trusted users → https://git.io/vhnGB
MichaelRaskin has joined #nixos-borg
<jtojnar> why is this not evaluated? https://github.com/NixOS/nixpkgs/pull/41339
<jtojnar> according to graphana, there are three free evaluators
<jtojnar> and no waiting evals