!zghijEASpYQWYFzriI:nixos.org

Hydra

386 Members
109 Servers

Load older messages


SenderMessageTime
5 Dec 2022
@cole-h:matrix.orgcole-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:matrix.orgjackdkThanks very much.21:42:28
6 Dec 2022
@federicodschonborn:matrix.org@federicodschonborn:matrix.org joined the room.12:16:07
@schnecfk:ruhr-uni-bochum.de@schnecfk:ruhr-uni-bochum.de changed their profile picture.14:10:23
7 Dec 2022
@yinfeng:li7g.comYinfeng joined the room.09:10:18
9 Dec 2022
@terwiz:matrix.orgterwizSo, 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@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@linus:schreibt.jetztaarch64 should be no problem, but outside nixos will definitely be a lot more effort and probably pain than on nixos09:25:26
@linus:schreibt.jetzt@linus:schreibt.jetztWhy do you have to use Ubuntu? And what went wrong with using a container?09:26:50
@andreas.schraegle:helsinki-systems.deajs124 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:matrix.orgterwizOuch. 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@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@linus:schreibt.jetztBut if you've got it working then 🤷12:18:38
10 Dec 2022
@rimuru:gentoo.chat@rimuru:gentoo.chat changed their profile picture.00:27:50
11 Dec 2022
@vcunat:matrix.orgvcunat

🤔 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:matrix.orgvcunat Maybe #infra:nixos.org would be a better channel; I'm not sure. 09:44:56
@vcunat:matrix.orgvcunatRetrying 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:matrix.orgjackdk
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
@tompurl:destrocodpiece.wtfTom Purl (he/him) joined the room.15:52:13
13 Dec 2022
@pmc:piperswe.mePiper (she/they) changed their display name from pmc to Piper (she/they).22:59:47
14 Dec 2022
@nahfe:nahfe.xyz@nahfe:nahfe.xyz changed their display name from NAHFE to Herman.10:53:43
@alesya-h:nixos.devAlesya Huzik joined the room.11:15:18
@nahfe:nahfe.xyz@nahfe:nahfe.xyz changed their display name from Herman to NAHFE.11:30:39
@nahfe:nahfe.xyz@nahfe:nahfe.xyz changed their display name from NAHFE to Herman.11:32:58
15 Dec 2022
@lgcl:lgcl.de@lgcl:lgcl.de changed their profile picture.20:16:09
17 Dec 2022
@v0id:nltrix.net@v0id:nltrix.net

32mP:88|F:1|R:0|T:0] Events: 2909 
The following jobs failed:
+--------------------------------------+------------------------------+
| Job ID                               | Test File                    |
+--------------------------------------+------------------------------+
| 3446CDB2-7E2E-11ED-A687-F3FB89213249 | Hydra/Controller/User/ldap.t |
+--------------------------------------+------------------------------+

                                   Yath Result Summary
-----------------------------------------------------------------------------------------
     Fail Count: 1
     File Count: 89
Assertion Count: 1368
      Wall Time: 165.97 seconds
       CPU Time: 999.09 seconds (usr: 1.65s | sys: 0.27s | cusr: 839.02s | csys: 158.15s)
      CPU Usage: 601%
    -->  Result: FAILED  <--
17:17:38
@v0id:nltrix.net@v0id:nltrix.netwhat am I missing I wonder.17:17:48
@v0id:nltrix.net@v0id:nltrix.netnix/store/0z75gl8v3anz9rcf6bn3sq9cqyh7521r-hydra-2022-11-24.drv17:18:13
@rick:matrix.ciphernetics.nlRick (Mindavi)Unstable test18:13:34
@qyliss:fairydust.spaceAlyssa RossHi! Could Hydra builders please be updated to at least these kernel versions, to resolve an issue where all i686 NixOS tests are failing to build? https://github.com/NixOS/nixpkgs/pull/206163#issuecomment-135640438519:31:54

Show newer messages


Back to Room ListRoom Version: 6