| 1 Dec 2022 |
 ajs124 | In reply to @janne.hess:helsinki-systems.de
I don't think it makes any sense. It pushes the required store paths to builders anyway and substituting from itself will never yield any success by default, the builders do substitute tho.
it's like nix-copy-close -s. | 12:35:08 |
|  hexa changed their display name from hexa to hexa (22.11 now). | 13:08:37 |
| hexa changed their display name from hexa (22.11 now) to hexa. | 14:38:26 |
 Sandro | How do I reset an error message like?
Aborted: [31;1merror:[0m a '[35;1mx86_64-linux[0m' with features {[35;1mgccarch-skylake[0m} is required to build '[35;1m/nix/store/fykll0wrfya0zqw51nsi9jbi0lasyfaa-closure-info.drv[0m', but I am a '[35;1mx86_64-linux[0m' with features {[35;1mgccarch-haswell, gccarch-ivybridge, gccarch-sandybridge, gccarch-westmere[0m} (log, raw, tail)}
Clear failed builds cache does not seem to do anything. Also why is hydra trying to build this on localhost?
My hydra machines file looks like localhost x86_64-linux - 4 5 gccarch-haswell,gccarch-ivybridge,gccarch-sandybridge,gccarch-westmere - -
| 15:00:06 |
| 3 Dec 2022 |
 ma27 | does anybody want to take a look at https://github.com/NixOS/hydra/pull/1263? %) | 12:10:50 |
| 4 Dec 2022 |
|  @schnecfk:ruhr-uni-bochum.de changed their display name from CRTified to CRTified (old handle). | 14:19:49 |
| 5 Dec 2022 |
 jackdk | In reply to @cole-h:matrix.org
You're looking for an "aggregate" job. There are some examples in Nixpkgs, I believe (look for `release.nix` or similarly-named files in `nixos/`). Also present in the Nix (the tool) flake, and probably the Hydra flake / repo as well. Thanks Cole, this does look like what I need. | 00:22:06 |
| jackdk | What's the status of determinate's terraform hydra provider? I see a few open PRs and a latest commit on main from August - is it under active development internally, feature complete, something else? | 00:24:50 |
 cole-h | In reply to @jackdk:matrix.org
What's the status of determinate's terraform hydra provider? I see a few open PRs and a latest commit on main from August - is it under active development internally, feature complete, something else? (This is my personal opinion, not that of my employer) I consider it fairly feature complete. 2 of the 3 draft PRs that touch the actual provider depend on upstream PRs being merged. That 3rd draft PR implements support for something that has been merged upstream, but I just never got around to finishing it 🤷 | 16:31:46 |
| jackdk | Thanks very much. | 21:42:28 |
| 6 Dec 2022 |
|  @federicodschonborn:matrix.org joined the room. | 12:16:07 |
| @schnecfk:ruhr-uni-bochum.de changed their profile picture. | 14:10:23 |
| 7 Dec 2022 |
|  Yinfeng joined the room. | 09:10:18 |
| 9 Dec 2022 |
 terwiz | So, after fiddling around with containerized hydra on aarch64 server and trying to get it working as a builder (and not really getting anywhere with that), we decided to go for a hydra (master) running directly on ubuntu+nix without containers. All docs I have found so far talk about installation on x86 and nixos. Any pointers to docs about installation on ubuntu+nix and/or aarch64, would be appreciated. | 08:31:52 |
 @linus:schreibt.jetzt | In reply to @terwiz:matrix.org
So, after fiddling around with containerized hydra on aarch64 server and trying to get it working as a builder (and not really getting anywhere with that), we decided to go for a hydra (master) running directly on ubuntu+nix without containers. All docs I have found so far talk about installation on x86 and nixos. Any pointers to docs about installation on ubuntu+nix and/or aarch64, would be appreciated. That sounds like a path of great resistance. I don't think anyone really does that :/ | 09:14:42 |
| @linus:schreibt.jetzt | aarch64 should be no problem, but outside nixos will definitely be a lot more effort and probably pain than on nixos | 09:25:26 |
| @linus:schreibt.jetzt | Why do you have to use Ubuntu? And what went wrong with using a container? | 09:26:50 |
| ajs124 | theoretically, you should be able to do what the NixOS module does manually/with whatever config management tool you use. I agree with Linux Hackerman tho. It sounds painful. | 09:35:54 |
| terwiz | Ouch. Well, the server is in AWS and NixOS was not on the premade image list (surprise, surprise). and the server is up and running already. This setup was/is just fine for doing manual builds, and those are still happening, so can't just reinstall everything.
With dockerized hydra I suppose the main issue was the /nix/store setup. Also, the nixos/hydra docker image is actually ubuntu + nix and not nixos. So I was also finding it difficult to configure, as all the instructions are for setting etc/nixos/configuration.nix and you don't have that in ubuntu + nix. That's also why I asked for pointers to docs, I expect the same issue without the docker... | 11:23:38 |
| @linus:schreibt.jetzt | In reply to @terwiz:matrix.org
Ouch. Well, the server is in AWS and NixOS was not on the premade image list (surprise, surprise). and the server is up and running already. This setup was/is just fine for doing manual builds, and those are still happening, so can't just reinstall everything.
With dockerized hydra I suppose the main issue was the /nix/store setup. Also, the nixos/hydra docker image is actually ubuntu + nix and not nixos. So I was also finding it difficult to configure, as all the instructions are for setting etc/nixos/configuration.nix and you don't have that in ubuntu + nix. That's also why I asked for pointers to docs, I expect the same issue without the docker... The NixOS foundation publishes NixOS AMIs though | 12:17:49 |
| @linus:schreibt.jetzt | But if you've got it working then 🤷 | 12:18:38 |
| 10 Dec 2022 |
|  @rimuru:gentoo.chat changed their profile picture. | 00:27:50 |
| 11 Dec 2022 |
 vcunat | 🤔 Hydra.nixos.org is now sometimes throwing eval errors like
{UNKNOWN}: aggregate job ‘tested’ failed with the error: nixos.tests.installer.swraid.x86_64-linux: error: cannot connect to socket at '/nix/var/nix/gc-socket/socket': No such file or directory
at /nix/store/j96zrgb48aiwxysh1vhq1zp1zv4da29r-hydra-perl-deps/lib/perl5/site_perl/5.34.1/Catalyst/Model/DBIC/Schema.pm line 526
| 09:44:27 |
| vcunat | Maybe #infra:nixos.org would be a better channel; I'm not sure. | 09:44:56 |
| vcunat | Retrying evaluation seems to fix it so far, but that can get annoying in the big jobsets where eval can take roughly an hour. | 09:45:58 |
| 12 Dec 2022 |
| jackdk | In reply to @terwiz:matrix.org
Ouch. Well, the server is in AWS and NixOS was not on the premade image list (surprise, surprise). and the server is up and running already. This setup was/is just fine for doing manual builds, and those are still happening, so can't just reinstall everything.
With dockerized hydra I suppose the main issue was the /nix/store setup. Also, the nixos/hydra docker image is actually ubuntu + nix and not nixos. So I was also finding it difficult to configure, as all the instructions are for setting etc/nixos/configuration.nix and you don't have that in ubuntu + nix. That's also why I asked for pointers to docs, I expect the same issue without the docker... aws ec2 describe-images --filters Name=owner-id,Values=080433136561 lists all amis published by the nixos org | 11:39:15 |
|  Tom Purl (he/him) joined the room. | 15:52:13 |
| 13 Dec 2022 |
|  Piper (she/they) changed their display name from pmc to Piper (she/they). | 22:59:47 |
| 14 Dec 2022 |
|  @nahfe:nahfe.xyz changed their display name from NAHFE to Herman. | 10:53:43 |
|  Alesya Huzik joined the room. | 11:15:18 |
