On 11 August 2013 20:12, phree...@yandex.ru wrote:
В письме от Воскресенье 11 августа 2013 16:55:54 пользователь Bjørn Forsman
написал:
It seems I've committed something that breaks the channel (sorry!).
Hydra has these evaluation errors[1]:
[...]
at
On 11 August 2013 20:30, Bjørn Forsman bjorn.fors...@gmail.com wrote:
So, what to do now? Start by changing the mit license to a string and
then wait for Eelco to decide what to do with the rest?
I took the simplest route: don't use the MIT license (for now).
Hi,
On 04/08/13 22:35, Bjørn Forsman wrote:
The channel doesn't update because virtualbox-image won't build
(out-of-memory):
Thanks. I've doubled the available memory size, hopefully that will prevent this
from happening again.
--
Eelco Dolstra | LogicBlox, Inc. | http://nixos.org/~eelco/
Perhaps add some monitoring?
Den 5 aug 2013 14:53 skrev Eelco Dolstra eelco.dols...@logicblox.com:
Hi,
On 04/08/13 22:35, Bjørn Forsman wrote:
The channel doesn't update because virtualbox-image won't build
(out-of-memory):
Thanks. I've doubled the available memory size, hopefully that
Hi,
On 05/08/13 14:55, Malcolm Matalka wrote:
Perhaps add some monitoring?
The build failure *is* the monitoring.
--
Eelco Dolstra | LogicBlox, Inc. | http://nixos.org/~eelco/
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
On 5 August 2013 15:02, Eelco Dolstra eelco.dols...@logicblox.com wrote:
Hi,
On 05/08/13 14:55, Malcolm Matalka wrote:
Perhaps add some monitoring?
The build failure *is* the monitoring.
Maybe build failures that block channel updates should result in a
notification email to nix-dev
Hi,
The channel doesn't update because virtualbox-image won't build (out-of-memory):
zmy56d4hplb5m69xsd99ma81kjvr34cx-systemd-203/example/sysctl.d/50-default.conf
zmy56d4hplb5m69xsd99ma81kjvr34cx-systemd-203/example/systemd/
rsync:
Hi,
On 19/07/13 20:15, Bjørn Forsman wrote:
Here is one more of those mysterious build errors in hydra that
cannot be reproduced locally (at least my machine built it just fine):
http://hydra.nixos.org/build/5567300/nixlog/1/tail-reload
Fixed, see
On 23 July 2013 11:19, Eelco Dolstra eelco.dols...@logicblox.com wrote:
Hi,
On 19/07/13 20:15, Bjørn Forsman wrote:
Here is one more of those mysterious build errors in hydra that
cannot be reproduced locally (at least my machine built it just fine):
On 19 July 2013 21:01, Malcolm Matalka mmata...@gmail.com wrote:
Are you compiling locally with chroot on?
I did one build with hydra's reproduce locally script. I don't know
if that uses chroot or not.
Then I built the failing expression (on hydra at least), netpbm, using
nix-build -A netpbm.
On 19 July 2013 23:51, Domen Kožar do...@dev.si wrote:
FYI: I also added netpbm to channel:
http://hydra.nixos.org/build/5567643/log/raw
And that build log ends in:
[q[pbuilding standardppmdfont.c
[3s[appmdcfont standard.ppmdfont standardppmdfont.c[b
/bin/sh: ppmdcfont: command not found
FYI: I also added netpbm to channel:
http://hydra.nixos.org/build/5567643/log/raw
On Fri, Jul 19, 2013 at 9:04 PM, Bjørn Forsman bjorn.fors...@gmail.comwrote:
On 19 July 2013 21:01, Malcolm Matalka mmata...@gmail.com wrote:
Are you compiling locally with chroot on?
I did one build with
On 19 July 2013 21:21, Malcolm Matalka mmata...@gmail.com wrote:
It doesn't, you have to turn it in the nix config since it is how the
builder runs.
In NixOS you have to do:
nix.useChroot = true;
Ok. I did that and ran nixos-rebuild switch. But when I try to build
it *without* using the
Hi,
Here is one more of those mysterious build errors in hydra that
cannot be reproduced locally (at least my machine built it just fine):
http://hydra.nixos.org/build/5567300/nixlog/1/tail-reload
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
Hi,
the following error shows up in may logfiles every few seconds from
Hydra 0.1pre1331-4b1a838:
[4-1] ERROR: column me.active does not exist at character 40
[4-2] STATEMENT: SELECT me.project, me.jobset, me.name, me.active,
me.errormsg, me.firstevaltime, me.lastevaltime FROM Jobs me
Hi.
On 04/24/2013 10:00 AM, Vladimír Čunát wrote:
Now there's a more serious issue:
http://hydra.nixos.org/build/4664332
it seems that directly hydra can't write new files.
There are still/again some out-of-space problems on the build farm.
This seems to happen a lot, any chance some simple program could be
installed to warn the maintainers of this so they can get to it in time?
Vladimír Čunát vcu...@gmail.com writes:
Hi.
On 04/24/2013 10:00 AM, Vladimír Čunát wrote:
Now there's a more serious issue:
It's time to package munin :)
On Wed, May 1, 2013 at 11:52 AM, Malcolm Matalka mmata...@gmail.com wrote:
This seems to happen a lot, any chance some simple program could be
installed to warn the maintainers of this so they can get to it in time?
Vladimír Čunát vcu...@gmail.com writes:
On 04/24/2013 10:00 AM, Vladimír Čunát wrote:
There are no route to host problems with the two FreeBSD machines.
Now there's a more serious issue:
http://hydra.nixos.org/build/4664332
it seems that directly hydra can't write new files.
We've been rebuilding quite a lot in the last few weeks.
It works.
Thank you.
M.
2013/4/12 Rob Vermaas rob.verm...@gmail.com:
The hydra manual at
http://hydra.nixos.org/job/hydra/trunk/tarball/latest/download-by-type/doc/manual
says in 2.5:
If you're upgrading Hydra from a previous version, you should do the
following to perform any
Hi,
I'm trying to upgrade my hydra server from an old version (3/4 months).
I successfully migrated the nix configuration but it seems that I need
to upgrade the database schema.
Can you suggest what I have to do in detail?
Here is the error I get
DBIx::Class::ResultSet::search(): DBI
Hi.
On 04/10/2013 03:58 PM, Eelco Dolstra wrote:
The gnucash job no longer exist, instead there are now jobs
named gnucash.i686-linux and so on.
A side note: you remind me some problems I've encountered with
hydra.nixos.org.
- The job status tab now makes less sense. There's a table, but
On 04/05/2013 10:00 PM, Vladimír Čunát wrote:
Good. Is it easy to clear negative caching for some jobs? On x-updates
there was a jump of about +3k fails about the time.
I mean, on x-updates, there are currently 4k failing jobs, so restarting
all of them shouldn't be such a deal if 3k of them
Hello,
I hit a case-sensitivity issue with Hydra on PostgreSQL 8.4:
http://thread.gmane.org/gmane.comp.lang.perl.modules.dbi.general/16888
Normally case-sensitivity isn’t an issue because DBIC doesn’t quote
identifiers. However, it does quote them when looking for a sequence,
hence the
Hi,
it appears that Hydra is offline. Now, every time I try to install a
package, nix-env hangs for a long time, probably until it's running into
some kind of network timeout. It used to be possible to work around this
issue by running
NIX_HASHED_MIRRORS= nix-env -i ...
..., but it seems
Hi,
On 06/02/13 10:51, Peter Simons wrote:
it appears that Hydra is offline.
Nixos.org is back up. (Note that this has nothing to do with Hydra. The Nix
binary cache / tarball mirror uses nixos.org, not hydra.nixos.org.)
Now, every time I try to install a
package, nix-env hangs for a long
Hi,
hydra is showing a strange evaluation error in x-updates
http://hydra.nixos.org/jobset/nixpkgs/xorg-test#tabs-errors
I've been unable to reproduce it on my machine and the hydra error
doesn't seem to say anything specific. What is the closest way to
simulate hydra evaluation?
Thanks,
Hi,
hydra trunk jobset shows a couple of obscure errors:
error: substituter
`/nix/store/xfh5mqan98jxr768kfjs201618sm34dv-nix-1.2pre3002_a7b4aaa/libexec/nix/substituters/download-from-binary-cache.pl'
failed: DBD::SQLite::st execute failed: database is locked at
Hi Yury et al,
I'm investigating these hydra evaluation errors:
Florian Friesdorf f...@chaoflow.net writes:
hydra has evaluation errors for the nixpkgs/trunk jobset[1]
at `leiningen' [system = x86_64-freebsd]:
assertion failed at
On 3 декабря 2012 09:38:25 Florian Friesdorf wrote:
Hi Yury et al,
I'm investigating these hydra evaluation errors:
Feel free to fix it in any way. Unfortunately, I have some problems with my
health and busy at my day job. Not too serious, but I will not be able to do
anything but my day
Hi Rob et al,
the situation improved, but hydra still runs out of disk space for
manual and simple installation test (x86_64).
It would be great to get hydra back to build our channel.
How can I help?
If we are short of resources, I'm happy to donate money if it gets us
more resources.
Hi,
On 29/11/12 11:38, Florian Friesdorf wrote:
the situation improved, but hydra still runs out of disk space for
manual and simple installation test (x86_64).
I've restarted these.
--
Eelco Dolstra | LogicBlox, Inc. | http://nixos.org/~eelco/
It seems it didn't
Please browse back a bit from http://hydra.nixos.org/view/nixos/tested
You'll notice that in the past 10 days or so, there have been a lot of
failures due to disk space. Waiting a night did not do the trick in most
cases, as errors persisted past date-borders.
On Tue, Nov
Hm, weird, I will look into it.
Cheers,
Rob
On Wed, Nov 28, 2012 at 1:16 PM, Mathijs Kwik math...@bluescreen303.nlwrote:
It seems it didn't
Please browse back a bit from http://hydra.nixos.org/view/nixos/tested
You'll notice that in the past 10 days or so, there have been a lot of
Hi,
hydra has evaluation errors for the nixpkgs/trunk jobset[1]
Two were caused by a wrong license name, which I could fix. Left are two
assertions errors and many caused by unsupported platform for Mesa
(see below).
Any hints how to fix these?
Example evaluation errors:
at
Hi all,
Builds are failing on hydra and the logs show issues with disk space.
Also, a lot of sqlite db busy warnings pop up, but I was told these
are harmless.
http://hydra.nixos.org/build/3336787
Can anyone free up some space / garbage collect the build farm?
Or will this be run as a cronjob
All hydra build machines have nightly garbage collects, I think of about
100-200G. Perhaps it was a busy day and filled disk up. Currently the
machine looks fine. Thanks for the report.
Cheers,
Rob
On Sun, Nov 18, 2012 at 2:01 PM, Mathijs Kwik math...@bluescreen303.nlwrote:
Hi all,
Builds
Hi guys,
the NixOS/Nixpkgs channel still doesn't have my 'amdUcode' patch from
last Tuesday:
| $ nix-channel --update nixos-rebuild dry-run
| fetching list of Nix archives at
`http://nixos.org/releases/nixos/nixos-0.1pre3776_34e8f68-894fad3/MANIFEST.bz2'...
| % Total% Received % Xferd
Hi,
On 03/07/12 04:01, Peter Simons wrote:
the NixOS/Nixpkgs channel still doesn't have my 'amdUcode' patch from
last Tuesday:
That's because one of the tests failed. See
http://hydra.nixos.org/view/nixos/tested/ (slow!). Now that that has been
fixed, there is a new release:
Den 2012-04-18 18:06:10 skrev Eelco Dolstra eelco.dols...@logicblox.com:
Hi,
On 18/04/12 17:45, Rickard Nilsson wrote:
So, if I maintain a set of changes to nixos and nixpkgs in /etc/nixos I
have to build and activate nixos manually, rather than with
nixos-rebuild?
You just have to
Hi,
On 17/04/12 19:07, Peter Simons wrote:
nixos-rebuild wants to compile lots of packages that I would expect to
get from hydra in binary form (such as Ghostscript), but apparently
Hydra doesn't have them? My manifest seems to be up-to-date, though:
# nixos-rebuild pull
fetching list
18 apr 2012 kl. 09:57 skrev Eelco Dolstra eelco.dols...@logicblox.com:
I should mention that there is also a NixOS channel now, containing both the
NixOS/Nixpkgs sources and the Nixpkgs binaries for Linux. To use it:
$ nix-channel --add
Hi,
On 18/04/12 17:45, Rickard Nilsson wrote:
So, if I maintain a set of changes to nixos and nixpkgs in /etc/nixos I have
to build and activate nixos manually, rather than with nixos-rebuild?
You just have to add -I /etc/nixos to the nixos-rebuild call.
It would be fancy if Hydra could
Hi,
nixos-rebuild wants to compile lots of packages that I would expect to
get from hydra in binary form (such as Ghostscript), but apparently
Hydra doesn't have them? My manifest seems to be up-to-date, though:
# nixos-rebuild pull
fetching list of Nix archives at
2012/2/20 Peter Simons sim...@cryp.to:
Hi,
the build http://hydra.nixos.org/build/2099429 of haskell-gtk+ failed
because the build machine ran out of disk space. This failure caused a
whole lot of other builds to fail, so I wonder whether someone could
re-start that build, please?
Take
I am also not a fan of removing things. Besides, we can hide projects and
jobsets already when 'they are in the way'.
On Mon, Jan 16, 2012 at 10:54, Eelco Dolstra e.dols...@tudelft.nl wrote:
Hi,
On 16/01/12 00:11, Yury G. Kudryashov wrote:
What do you think about removing old jobsets from
Hi!
What do you think about removing old jobsets from hydra?
E.g., when I see kde47 I decide that trunk defaults to kde-4.8 (will be
released in a week). And xorg-test says nothing about X.Org version.
--
Yury G. Kudryashov,
mailto: ur...@mccme.ru
Hi,
BLCR supports linux kernel up to version 2.6.38.
How I am supposed to signal this fact to hydra?
(So it avoids to start compilations that will inevitably fail.)
Can an assert be good enough for this?
Thanks,
Marco
On Oct 12, 2011, at 2:23 PM, Hydra Build Daemon wrote:
Hi,
This is to
Marco Maggesi wrote:
Hi,
BLCR supports linux kernel up to version 2.6.38.
How I am supposed to signal this fact to hydra?
(So it avoids to start compilations that will inevitably fail.)
Can an assert be good enough for this?
Why does hydra build blcr at all? It neither has meta.platforms
201 - 249 of 249 matches
Mail list logo
