Re: [Nix-dev] Hydra queue is in a weird state

Hi, On 06/12/2017 01:51 PM, Vladimír Čunát wrote: > Just to be sure, the binaries from staging are cached at least for a few > days, right? Right now, there is no garbage collection of the cache.nixos.org S3 bucket *at all*, so binaries are kept indefinitely. -- Eelco Dolstra | LogicBlox,

Re: [Nix-dev] Hydra queue is in a weird state

On 06/12/2017 11:23 AM, Eelco Dolstra wrote: > Can you be more specific (e.g. build IDs)? I don't see anything wrong at the > moment. Hmm, me neither, not anymore. The number of queued jobs on trunk* has also dropped to the number I would expected right after the merge and I see no particular

Re: [Nix-dev] Hydra queue is in a weird state

Hi, On 06/12/2017 08:17 AM, Vladimír Čunát wrote: > around 24h ago I merged some older staging commit, and Hydra somehow > hasn't recovered since. > > Most of jobs should've been cached from staging - mainly except for > Haskell stuff because that got updated on master in the meantime - but >

[Nix-dev] Hydra queue is in a weird state

Hi, around 24h ago I merged some older staging commit, and Hydra somehow hasn't recovered since. Most of jobs should've been cached from staging - mainly except for Haskell stuff because that got updated on master in the meantime - but apparently those jobs are stuck in the queue, not being

Re: [Nix-dev] Hydra and security updates

On 17-06-04 12:35am, Nicolas Pierron wrote: > So currently, this project is held by a dead-lock between people > asking me to demonstrate a large scale example, and having the > infrastructure to doing so. I think most of the lockup stems from people not really knowing what your framework means

Re: [Nix-dev] Hydra and security updates

On Sun, Jun 4, 2017 at 1:17 AM, Bjørn Forsman wrote: > On 4 June 2017 at 00:35, Nicolas Pierron wrote: >> So I started SOS [1] to make Nixpkgs more >> declarative. Thus removing some of the function overhead from >> packages, which would help

Re: [Nix-dev] Hydra and security updates

On 4 June 2017 at 00:35, Nicolas Pierron wrote: > So I started SOS [1] to make Nixpkgs more > declarative. Thus removing some of the function overhead from > packages, which would help fixing a lot of the issues reported by the > static-analysis. I think you forgot

Re: [Nix-dev] Hydra and security updates

On Sat, Jun 3, 2017 at 1:26 PM, Graham Christensen wrote: > This is part of my inclination of not really loving PR#10851, it is > complicated and goes around the normal proceses, even when we can easily > deploy fairly quickly. The problem that I have with the current

Re: [Nix-dev] Hydra and security updates

On Sat, Jun 3, 2017 at 12:54 AM, Leo Gaspard wrote: > On 06/02/2017 12:05 PM, Domen Kožar wrote: >>> I see two ways of doing this: either having hydra somehow handle with >>> special care security updates (hard to do) >> >> https://github.com/NixOS/nixpkgs/pull/10851 > > This

Re: [Nix-dev] Hydra and security updates

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Leo Gaspard writes: > I just wanted to point out an issue with hydra: it doesn't make any > distinction between security updates and normal changes. > > For example, [1] was released two days ago. Despite the fix landing two >

Re: [Nix-dev] Hydra and security updates

So, the assumption is: "security updates hardly should break stuff, so we can apply them without tests" And desire is: "don't publish untested changes to channel" This clearly leads to necessity of two channels, just as described in

Re: [Nix-dev] Hydra and security updates

On 06/03/2017 01:55 AM, Frank wrote: > Op 3-6-2017 om 0:59 schreef Leo Gaspard: >> On 06/02/2017 06:54 PM, Frank wrote: >>> Op 1-6-2017 om 23:32 schreef Leo Gaspard: Hi all, I just wanted to point out an issue with hydra: it doesn't make any distinction between security updates

Re: [Nix-dev] Hydra and security updates

Op 3-6-2017 om 0:59 schreef Leo Gaspard: On 06/02/2017 06:54 PM, Frank wrote: Op 1-6-2017 om 23:32 schreef Leo Gaspard: Hi all, I just wanted to point out an issue with hydra: it doesn't make any distinction between security updates and normal changes. Why is this an issue? Security-updates

Re: [Nix-dev] Hydra and security updates

> > For that we'd need to have infrastructure that builds PRs and reports > status on github. > > I think that's the right solution, but it does involve work and Hydra > improvements :) Hmm, "[Nix-dev] Hydra Building PRs" (2017-01-28) made me think hydra was actual

Re: [Nix-dev] Hydra and security updates

Op 1-6-2017 om 23:32 schreef Leo Gaspard: Hi all, I just wanted to point out an issue with hydra: it doesn't make any distinction between security updates and normal changes. Why is this an issue? Security-updates are just as likely to introduce bugs as every other update. Greetings,

Re: [Nix-dev] Hydra and security updates

> I see two ways of doing this: either having hydra somehow handle with > special care security updates (hard to do) https://github.com/NixOS/nixpkgs/pull/10851 > , or having master and stable branches *always* build. For that we'd need to have infrastructure that builds PRs and reports status

Re: [Nix-dev] Hydra and security updates

On Thu, Jun 1, 2017, at 23:32, Leo Gaspard wrote: > Hi all, > > [ ... ] I think this is relevant to your interests: https://github.com/NixOS/nixpkgs/pull/10851 On a side note, I don't know why anybody would actually run nixos-unstable; it gets stuck for long periods of time quite often ... I

[Nix-dev] Hydra and security updates

Hi all, I just wanted to point out an issue with hydra: it doesn't make any distinction between security updates and normal changes. For example, [1] was released two days ago. Despite the fix landing two days ago too [2], nixos-unstable still doesn't have the vulnerability fixed. Granted, in

Re: [Nix-dev] hydra problems

On 05/30/2017 12:29 PM, Danylo Hlynskyi wrote: > 1. https://hydra.nixos.org seems to have problems with HTTPS: in my > Firefox. I can't reproduce that. Perhaps some transient problem? > 2. no build results can be downloaded They aren't stored on Hydra (for months, maybe a couple years now). I

[Nix-dev] hydra problems

1. https://hydra.nixos.org seems to have problems with HTTPS: in my Firefox. 2. no build results can be downloaded ___ nix-dev mailing list nix-dev@lists.science.uu.nl https://mailman.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Hydra: no space on aarch64

Hi, Thank you for letting me know. I've corrected the configuration on the aarch64 box to run garbage collection. It seems a typo prevented it from running. Best, Graham On Fri, May 26, 2017 at 4:49 AM Vladimír Čunát wrote: > Another problem: the "mac2" slave is killing all

Re: [Nix-dev] Hydra: no space on aarch64

Another problem: the "mac2" slave is killing all builds, with download-from-binary-cache.pl getting "curl error 60" and consequently a segfault. (if I interpret it right) ___ nix-dev mailing list nix-dev@lists.science.uu.nl

[Nix-dev] Hydra: no space on aarch64

Hi, the aarch64 machine has been out of space for the past few days at least, failing whatever builds it attempted. It doesn't seem like it will fix itself (this time). --Vladimir ___ nix-dev mailing list nix-dev@lists.science.uu.nl

Re: [Nix-dev] Hydra is down?

On 03/12/2017 06:50 PM, Michael Alan Dorman wrote: > The web interface at least hasn't been available for a number of hours. Yes, basically the whole weekend, I think. I expect admins will be fixing this during Monday's morning (but I'm just guessing from past experience). --Vladimir

[Nix-dev] Hydra is down?

The web interface at least hasn't been available for a number of hours. ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Hydra Building PRs

Heh, I've been working on this as well today. Do you have a github repo somewhere? 2017-03-07 14:27 GMT+01:00 Robin Gloster : > I'm working on a bot to make sure only acknowledged PRs get built. > > That is a bit on hold until the release probably but I'm going to continue >

Re: [Nix-dev] Hydra Building PRs

I'm working on a bot to make sure only acknowledged PRs get built. That is a bit on hold until the release probably but I'm going to continue that definitely. That bot could then also include stuff like mentioning the correct maintainers, auto merging if the builds succeed, security tracking

Re: [Nix-dev] Hydra Building PRs

Bas van Dijk writes: > Hi Graham, what's te status of this project? Great question. Dezgeg and I are working on bootstrapping some ARM machines now, at which point I'll be working with Eelco to add them to Hydra. I don't have an ETA, but finding a compatible time between

Re: [Nix-dev] Hydra Building PRs

As a stop-gap measure, what about adding an external SSD drive via usb and enabling swap? 2017-03-06 16:33 GMT+01:00 Bas van Dijk : > On 28 January 2017 at 14:20, Graham Christensen > wrote: > >> Packet.net is also one of the only hosting companies I

Re: [Nix-dev] Hydra Building PRs

On 28 January 2017 at 14:20, Graham Christensen wrote: > Packet.net is also one of the only hosting companies I know of which > rents Cavium ThunderX ARMv8s, and they're very interested in our > supporting this architecture. Soon, with the help of Dezgeg, > prs.nix.gsc.io

Re: [Nix-dev] hydra build for qtwebengine stuck

On 02/20/2017 06:47 PM, Michael Alan Dorman wrote: > The latest attempt to build qtwebengine has failed for reasons > (http://hydra.nixos.org/build/49045866/nixlog/1/tail-reload) that are > ultimately environmental---but appear to mean that it won't get retried > automatically. There's only

[Nix-dev] hydra build for qtwebengine stuck

The latest attempt to build qtwebengine has failed for reasons (http://hydra.nixos.org/build/49045866/nixlog/1/tail-reload) that are ultimately environmental---but appear to mean that it won't get retried automatically. What's the best way to report or address such failures? Here on the list, as

Re: [Nix-dev] Hydra Building PRs

On 30-01-2017 21:28:11, Graham Christensen wrote: > > SIDE NOTE: I'm considering making a bot which comments on PRs with a > link to their jobset. Unless someone objects, I'll go ahead and do so. > PLEASE go ahead! I'd love to get notifications like this! Also, you could email the author of

Re: [Nix-dev] Hydra Building PRs

That's excellent to get the integration tests running! As for the comment. If it's not too much work it would be great to integrate it with the status API (I think that's what it is called). It is much tydier and it's nice to get the pass/fail status highlighted in the UI.

Re: [Nix-dev] Hydra Building PRs

Update: Before now, PRs were being built using the nixpkgs release.nix. As of https://github.com/grahamc/hydra-prs/commit/df790c5c7f36bc0b0f033b1caf9c3188ddfa4065 all builds are being performed now on the NixOS release-combined.nix. This means each push will trigger affected tests to run in

Re: [Nix-dev] Hydra Building PRs

You know what they say: inodes make a fool of us all. I collected garbage and that should fix it / trigger an evaluation on next push to the PR. I've also enabled auto GC on the master (salves already had it.) I'll be pushing this confit change to the hydraprs repo soon. Note stats are

Re: [Nix-dev] Hydra Building PRs

Bas van Dijk writes: > Any idea what is going wrong? No idea :) The joys of Hydra! I'll check in to it :) ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Hydra Building PRs

This is just great work! I'm also very excited about the work on ARM. I do see one of my PRs failing to evaluate though: https://prs.nix.gsc.io/jobset/nixos/pr-22121#tabs-errors Any idea what is going wrong? Bas On 28 January 2017 at 14:20, Graham Christensen wrote: >

Re: [Nix-dev] Hydra Building PRs

On Jan 28, 2017 13:21, "Graham Christensen" wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello everyone, A couple weeks ago I created https://prs.nix.gsc.io/, a Hydra server which builds every PR. Every PR will exist at

[Nix-dev] Hydra Building PRs

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello everyone, A couple weeks ago I created https://prs.nix.gsc.io/, a Hydra server which builds every PR. Every PR will exist at https://prs.nix.gsc.io/jobset/nixos/pr-PRNUMBER. It features: - a web-hook, which means: - the moment a PR is

[Nix-dev] Hydra isn't seeing visitors again

It looks like hydra is busted: > (en) Please come back later Graham ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Hydra: infinite CPU and RAM consumption in evaluator

Christian Theune writes: > I’m fighting against getting a very current version of Hydra running, > as something blocks it from compiling. I’m guessing I need to override > GCC to GCC6, but the overrideCC drops me in an infinite recursion > (which doesn’t even look like an

Re: [Nix-dev] Hydra: infinite CPU and RAM consumption in evaluator

Hahaha, no, thanks. :) Infinite is 32G at the moment and we’re on an older version. It’s one of our own changes, most likely this one: https://github.com/flyingcircusio/nixpkgs/commit/2926129b8940e880a7745e44df511a3d6adacfa9

Re: [Nix-dev] Hydra: infinite CPU and RAM consumption in evaluator

Am 19.01.2017 um 11:12 schrieb Christian Theune: > Nevertheless, it looks like we may have introduced poisonous code that sends > the evaluator off into infinity. We’ll come back when we find out what it was. I got it and I would like to share my findings. We introduced a change that imported an

Re: [Nix-dev] Hydra: infinite CPU and RAM consumption in evaluator

Hi, ok, so the best way getting back to a working Hydra was the tip about running the system from a checkout and hydra from a checkout. Picking the versions from Hydra’s own Hydra job to see which ran fine resulted in a ~10day old nixpkgs and the most current Hydra version running properly.

Re: [Nix-dev] Hydra: infinite CPU and RAM consumption in evaluator

hi, jobsets changing can be broken for the moment, but thanks. Especially seeing that I need to go directly to head. Appreciated! Christian > On 18 Jan 2017, at 18:55, stewart mackenzie wrote: > > The next problem you will have is this: >

Re: [Nix-dev] Hydra: infinite CPU and RAM consumption in evaluator

see https://github.com/NixOS/hydra/issues/444 On Thu, Jan 19, 2017 at 1:53 AM, Christian Theune wrote: > Hi, > > On 18 Jan 2017, at 18:33, Jean-Pierre wrote: > > New version of hydra (2016-12-09) override gcc to gcc6 > >

Re: [Nix-dev] Hydra: infinite CPU and RAM consumption in evaluator

The next problem you will have is this: https://github.com/NixOS/hydra/issues/445 remove those changes and you will be able to add jobsets. ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Hydra: infinite CPU and RAM consumption in evaluator

Hi, > On 18 Jan 2017, at 18:33, Jean-Pierre wrote: > > New version of hydra (2016-12-09) override gcc to gcc6 > > https://github.com/NixOS/hydra/blob/aef048b3cb3a7db25b1c48366f266031c5905c0b/release.nix#L127 > >

[Nix-dev] Hydra: infinite CPU and RAM consumption in evaluator

Hi, our Hydra exploded today: after a recent change to our nixpkgs branch, we encountered the evaluator consuming infinite CPU and quite a lot of memory. Updating to a current version of Hydra (nixpkgs trunk) didn’t help. We’re going to go through the changes that caused this tomorrow.

Re: [Nix-dev] hydra local build failed

On 12.12.2016 13:39, Walter Franzini wrote: > Hi, > > I'm going to experiment with hydra and installing it in a nix > multi-user environment I get a compilation error: > > ... > g++ -DHAVE_CONFIG_H -I. -I../.. > -I/nix/store/xibmb4s2xah92zx2m34gng55in38l2cq-boehm-gc-7.2g-dev/include >

[Nix-dev] hydra local build failed

Hi, I'm going to experiment with hydra and installing it in a nix multi-user environment I get a compilation error: ... g++ -DHAVE_CONFIG_H -I. -I../.. -I/nix/store/xibmb4s2xah92zx2m34gng55in38l2cq-boehm-gc-7.2g-dev/include

[Nix-dev] Hydra Github Status Plugin

Hi, I am using Hydra for CI and I am loving it so far. However, it would be really nice to show the build status on Github. I see that there is a GithubStatus plugin in the Hydra source code, but I couldn't find any examples or documentation on how to use it. Is anybody using the

Re: [Nix-dev] Hydra stuck?

Hi, On 09/21/2016 02:04 AM, Michael Alan Dorman wrote: > At least the web interface doesn't appear to have changed anything in > the last 24 hours or so... Hydra-evaluator was hanging in a Mercurial checkout. I've restarted it. -- Eelco Dolstra | LogicBlox, Inc. | http://nixos.org/~eelco/

[Nix-dev] Hydra stuck?

At least the web interface doesn't appear to have changed anything in the last 24 hours or so... ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev

[Nix-dev] Hydra having problems?

It looks like there's a lot of idle machines, with nothing attempting to build? Mike. ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Hydra is down

On 07/31/2016 07:27 AM, Daniel Hlynskyi wrote: > https://hydra.nixos.org/ returns 500 Internal Server Error Now it's up again, after more than a day, I think. smime.p7s Description: S/MIME Cryptographic Signature ___ nix-dev mailing list

[Nix-dev] Hydra is down

https://hydra.nixos.org/ returns 500 Internal Server Error ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Hydra

Hi Fare, "Dev.Rideau.Fare" writes: > I'm trying to determine how feasible it would be (with how much work) > to use Hydra for a CI environment at work (replacing buildbot). we've been using hydra for about a year now. Not sure how does it compare to buildbot but

[Nix-dev] Hydra

Dear NixOS developers, I'm trying to determine how feasible it would be (with how much work) to use Hydra for a CI environment at work (replacing buildbot). * I don't see much documentation. Many links are dead or redirect to the wrong thing: the old 2008 paper mentions nixos.org/hydra-scp

Re: [Nix-dev] Hydra out of disk space

Maybe it would be a good idea to remove the old channels (13.10 up to 14.12). On 16-07-2016 11:50:32, Mateusz Czaplinski wrote: > Sorry if this was already discussed, but I had a thought recently, > that if the Hydra farm has recurring trouble with capacity, maybe > there is a chance some

Re: [Nix-dev] Hydra out of disk space

How much space does it currently take up? On 16 July 2016 at 11:50, Mateusz Czaplinski wrote: > Sorry if this was already discussed, but I had a thought recently, > that if the Hydra farm has recurring trouble with capacity, maybe > there is a chance some third-party

Re: [Nix-dev] Hydra out of disk space

Sorry if this was already discussed, but I had a thought recently, that if the Hydra farm has recurring trouble with capacity, maybe there is a chance some third-party company or individual would be willing to contribute hardware, e.g. if asked for help on Hacker News, twitter, etc. On Fri, Jul

Re: [Nix-dev] Hydra out of disk space

Hi all, I don't know if it's needed or not (you are probably aware), but here is a reminder that hydra builds are still failing due to "out of disk space". - Bjørn ___ nix-dev mailing list nix-dev@lists.science.uu.nl

Re: [Nix-dev] Hydra is down (500 Internal Server Error)

Now it works. - Bjørn ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev

[Nix-dev] Hydra is down (500 Internal Server Error)

This is what you get when visiting hydra.nixos.org: 500 Internal Server Error DBIx::Class::Storage::DBI::catch {...} (): DBI Connection failed: DBI connect('dbname=hydra;user=hydra;','',...) failed: could not connect to server: No such file or directory Is the server running locally and

Re: [Nix-dev] hydra and nixos versions/commits at hydra.nixos.org

On 20 Jun 2016 17:53, "Domen Kožar" wrote: > I do agree it's additional work, but it's better than current state where we all maintain our Hydra from carefully picked commits and that's REALLY some additional work. Completely agree, it's kind of annoying going through the commits

Re: [Nix-dev] hydra and nixos versions/commits at hydra.nixos.org

On Thu, Jun 16, 2016 at 2:50 PM, Tomasz Czyż wrote: > > > 2016-06-16 11:31 GMT+01:00 Domen Kožar : > >> On Thu, Jun 16, 2016 at 11:23 AM, Tomasz Czyż >> wrote: >> >>> Domen, >>> >>> do you know what's the strategy for hydra in nixos?

Re: [Nix-dev] hydra and nixos versions/commits at hydra.nixos.org

2016-06-16 11:31 GMT+01:00 Domen Kožar : > On Thu, Jun 16, 2016 at 11:23 AM, Tomasz Czyż > wrote: > >> Domen, >> >> do you know what's the strategy for hydra in nixos? Looks like module >> file is not imported from hydra but is copied/prepared separately in

Re: [Nix-dev] hydra and nixos versions/commits at hydra.nixos.org

On Thu, Jun 16, 2016 at 11:23 AM, Tomasz Czyż wrote: > Domen, > > do you know what's the strategy for hydra in nixos? Looks like module file > is not imported from hydra but is copied/prepared separately in nixos. That > means there are two module versions but one code

Re: [Nix-dev] hydra and nixos versions/commits at hydra.nixos.org

Domen, do you know what's the strategy for hydra in nixos? Looks like module file is not imported from hydra but is copied/prepared separately in nixos. That means there are two module versions but one code base. Will hydra module be moved to nixos? If not, maybe would be better to just import

Re: [Nix-dev] hydra and nixos versions/commits at hydra.nixos.org

Hi Domen, Domen Kožar writes: > Hydra NixOS module and package are now available on nixpkgs master. thank you! > There's one bug I need to fix, then I'll backport these changes to > 16.03. great! > Meanwhile, I used following commit on 16.03 before I moved to the > fork using

Re: [Nix-dev] hydra and nixos versions/commits at hydra.nixos.org

On Wed, Jun 15, 2016 at 3:40 AM, Domen Kožar wrote: > Hydra NixOS module and package are now available on nixpkgs master. > There's one bug I need to fix, then I'll backport these changes to 16.03. > > Meanwhile, I used following commit on 16.03 before I moved to the fork > using

Re: [Nix-dev] hydra and nixos versions/commits at hydra.nixos.org

Hydra NixOS module and package are now available on nixpkgs master. There's one bug I need to fix, then I'll backport these changes to 16.03. Meanwhile, I used following commit on 16.03 before I moved to the fork using some improvements:

[Nix-dev] hydra and nixos versions/commits at hydra.nixos.org

Hi, does somebody know, what hydra and nixos versions/commits are deployed at hydra.nixos.org? I am running hydra with nixos 15.09 and hydra 993647d1e3b43f1f9b7dc2ebce889b475d156bb9 but I would like to upgrade my local hydra machine to nixos 16.03. I can see that the last successful hydra build

Re: [Nix-dev] Hydra jobs from private git repositories

D'oh! Disabling StrictHostKeyChecking made it work perfectly, thanks! On 25 March 2016 at 23:28, Domen Kožar wrote: > See https://github.com/peti/hydra-tutorial/issues/2 > > On Fri, Mar 25, 2016 at 9:48 PM, Teo Klestrup Röijezon > wrote: > >> For the record, it

Re: [Nix-dev] Hydra jobs from private git repositories

See https://github.com/peti/hydra-tutorial/issues/2 On Fri, Mar 25, 2016 at 9:48 PM, Teo Klestrup Röijezon wrote: > For the record, it says something about host key verification failing. If > I try to run `ssh g...@bitbucket.org` sudoed as either user it works and > shows that

Re: [Nix-dev] Hydra jobs from private git repositories

For the record, it says something about host key verification failing. If I try to run `ssh g...@bitbucket.org` sudoed as either user it works and shows that it should have access to the repo. On 25 March 2016 at 22:47, Teo Klestrup Röijezon wrote: > Did that for both hydra

Re: [Nix-dev] Hydra jobs from private git repositories

Did that for both hydra and hydra-queue-runner, no luck. :/ On 25 March 2016 at 21:29, Oliver Charles wrote: > I've had luck just doing `sudo -u hydra -i` on the Hydra machine and > setting up id_rsa and friends in ~/.ssh. I think the full path is > /var/lib/hydra/.ssh. >

Re: [Nix-dev] Hydra jobs from private git repositories

I've had luck just doing `sudo -u hydra -i` on the Hydra machine and setting up id_rsa and friends in ~/.ssh. I think the full path is /var/lib/hydra/.ssh. On Fri, Mar 25, 2016 at 3:19 PM Teo Klestrup Röijezon wrote: > Hi, > > Is there any support for setting up Hydra jobs

[Nix-dev] Hydra jobs from private git repositories

Hi, Is there any support for setting up Hydra jobs with private git repositories as build inputs? I generated a SSH keypair each for hydra and hydra-queue-runner, and added them both as deploy keys on Bitbucket, but the authentication still seems to fail. This was using Hydra

[Nix-dev] hydra on ubuntu

Hi, Is anyone successfully running hydra on ubuntu? If so, could you provide me with some info/help on setting it up? In my current setup using NixOS in production is sadly not an option so I am trying to figure out if running hydra on ubuntu is feasible at all. My googling only unveiled an

Re: [Nix-dev] Hydra / Builder stability

Hi, ah, well. So I might try reducing the parallel build load on that machine and should see things improve, right? > On 02 Mar 2016, at 13:07, Eelco Dolstra wrote: > > Hi, > > On 02/03/16 08:32, Christian Theune wrote: > >> the Hydra server I run frequently has

Re: [Nix-dev] Hydra / Builder stability

Hi, On 02/03/16 08:32, Christian Theune wrote: > the Hydra server I run frequently has issues completing its jobs correctly. It > usually fails with weird issues but is fine when restarting. Here’s an > example: > https://hydra.flyingcircus.io/build/1623/nixlog/2/raw Looks like you restarted

[Nix-dev] Hydra / Builder stability

Hi, the Hydra server I run frequently has issues completing its jobs correctly. It usually fails with weird issues but is fine when restarting. Here’s an example: https://hydra.flyingcircus.io/build/1623/nixlog/2/raw I also had the

[Nix-dev] Hydra builds for Mac OS X

Hi, Lately the queue on hydra.nixos.org has been pretty full, mostly with Mac OS X related builds. To start the new year off with a bang, we have sextupled the build capacity for Mac OS X (x86_64-darwin), we have gone from 2 cores to 12 cores! This expansion was made possible by Dan Peebles,

Re: [Nix-dev] Hydra builds for Mac OS X

Sweet! Although I’m surprised that the Mac OS X queue is empty right now =) Christian > On 04 Jan 2016, at 19:40, Rob Vermaas wrote: > > Hi, > > Lately the queue on hydra.nixos.org has been pretty full, mostly with > Mac OS X related builds. To start the new year off

Re: [Nix-dev] Hydra builds for Mac OS X

They're so fast that they emptied the queue immediately! :) On Mon, Jan 4, 2016 at 4:02 PM, Christian Theune wrote: > Sweet! > > Although I’m surprised that the Mac OS X queue is empty right now =) > > Christian > > On 04 Jan 2016, at 19:40, Rob Vermaas

Re: [Nix-dev] Hydra builds for Mac OS X

Hi, > On 05 Jan 2016, at 00:17, Daniel Peebles wrote: > > They're so fast that they emptied the queue immediately! :) Haha :) — I didn’t quite believe that when looking at the total job numbers of the machines earlier. I also saw that there were a few darwin jobs but

Re: [Nix-dev] Hydra admins: ssh key change in a build slave

Hi, On 07/11/15 08:28, Vladimír Čunát wrote: > a notice in case you haven't seen/fixed it yet: ~21h ago we got some > abortions due to 52.30.94.163 changing ssh key (likely due to NixOS > update ;-). http://hydra.nixos.org/build/27399440 This was actually caused by hydra-provisioner not

[Nix-dev] Hydra admins: ssh key change in a build slave

Hi, a notice in case you haven't seen/fixed it yet: ~21h ago we got some abortions due to 52.30.94.163 changing ssh key (likely due to NixOS update ;-). http://hydra.nixos.org/build/27399440 Vladimir smime.p7s Description: S/MIME Cryptographic Signature

Re: [Nix-dev] hydra build failures

Hi, On 13/10/15 19:07, Christian Theune wrote: > In revision 82504fe01084f432443c121614532d29c781082a I get this error: > http://dpaste.com/2M8RJHB > > In revision 1a92f971d4648d942090e5a25b0b1e34be779a0b I get this: > http://dpaste.com/0G760R4 You need to update Nixpkgs to get the latest

Re: [Nix-dev] hydra build failures

> On 14 Oct 2015, at 12:57, Eelco Dolstra wrote: > > Hi, > > On 14/10/15 12:39, Christian Theune wrote: > >>> You need to update Nixpkgs to get the latest unstable Nix version, which >>> Hydra >>> requires. >> >> Ah, thanks. I didn’t think about *that* :) >> >>

Re: [Nix-dev] hydra build failures

It's really sad to me that we have Nix as a core tool to solve packaging problems and then we don't even release hydra and claim minimum versions required for it's dependencies. It gives a really bad taste to anyone who tries Nix stack and gets bitten on such trivial problem we claim to solve.

Re: [Nix-dev] hydra build failures

Hi, On 14/10/15 12:39, Christian Theune wrote: >> You need to update Nixpkgs to get the latest unstable Nix version, which >> Hydra >> requires. > > Ah, thanks. I didn’t think about *that* :) > > To learn something from this: what was the indicator to notice? Hydra build failures in C++ code

Re: [Nix-dev] hydra build failures

Hi, On 14/10/15 13:01, Domen Kožar wrote: > It's really sad to me that we have Nix as a core tool to solve packaging > problems and then we don't even release hydra and claim minimum versions > required for it's dependencies. Well, it's important to note that Hydra *is* unreleased software - it

Re: [Nix-dev] hydra build failures

Thanks. There are various companies/people using it in the wild, I see no reason why we couldn't release an alpha, just so people can install it successfully. On Wed, Oct 14, 2015 at 1:24 PM, Eelco Dolstra wrote: > Hi, > > On 14/10/15 13:01, Domen Kožar wrote: > >

Re: [Nix-dev] hydra build failures

Hi, > On 14 Oct 2015, at 11:23, Eelco Dolstra wrote: > > Hi, > > On 13/10/15 19:07, Christian Theune wrote: > >> In revision 82504fe01084f432443c121614532d29c781082a I get this error: >> http://dpaste.com/2M8RJHB >> >> In revision

Re: [Nix-dev] hydra build failures

> On 14 Oct 2015, at 13:32, Vladimír Čunát wrote: > > On 10/14/2015 01:24 PM, Eelco Dolstra wrote: >> Well, it's important to note that Hydra *is* unreleased software - it exists >> to >> do continuous builds for nixos.org, and I can't really make any claims about >> its >>

[Nix-dev] hydra build failures

Hi, I’m experiencing build failures with newer hydra versions. In revision 82504fe01084f432443c121614532d29c781082a I get this error: http://dpaste.com/2M8RJHB In revision 1a92f971d4648d942090e5a25b0b1e34be779a0b I get this: http://dpaste.com/0G760R4 The last revision that worked for me was:

  1   2   3   >