On Thu, Dec 10, 2015 at 02:05:56AM -0500, Leo Famulari wrote:
> python-urwid-1.3.0 fails to build on x86_64 during the
> "AsyncioEventLoopTest" test with the error "KeyError: '5 is not
> registered'". It has failed repeatedly for some time now. It fails in
> the same way when updated to python-urwi
python-urwid-1.3.0 fails to build on x86_64 during the
"AsyncioEventLoopTest" test with the error "KeyError: '5 is not
registered'". It has failed repeatedly for some time now. It fails in
the same way when updated to python-urwid-1.3.1.
I looked for interesting changes made between the last succe
Hi!
Jessica Tallon skribis:
> I just checked in Trisquel as I was curious what driver was being used
> there and `lsusb -t` shows the driver to be usbhid module. I confirmed
> this by unloading the module and verifying the keyboard stopped
> working.
>
> I did then boot the guix 0.9 installation
The gtk-doc builds started failing on all platforms when the following
security updates were added:
--8<---cut here---start->8---
* 3470fe0..: Mark H Weaver 2015-11-16 gnu: libsndfile: Add fixes for
CVE-2014-9496 and CVE-2015-7805.
* b4a88dc..: Mark H Weaver 20
In DMD, the "respawn.sh" test fails quite consistently on armhf, and has
sometimes failed on mips64el and x86_64 as well. Here's a copy of
test-suite.log from a recent failure on armhf:
--8<---cut here---start->8---
===
GNU dm
Alex Kost skribis:
> I install several xorg font packages (font-adobe75dpi, font-adobe100dpi,
> font-misc-misc and font-alias) in one of my profiles, and point my Xorg
> font path to this directory. Previously it worked fine, but after
> commit bf9655f¹, I cannot use this anymore, because the em
Over the last month, the 'python-matplotlib' build on armhf has failed
non-deterministically 4 times due to timeout (1 hour of silence) in the
same place:
--8<---cut here---start->8---
phase `install' succeeded after 71.4 seconds
starting phase `install-doc'
Run
In the last month, libical has non-deterministically failed twice, once
on i686 and once on mips64el, with the same error in the same place:
--8<---cut here---start->8---
[ 19%] Building C object
src/libicalss/CMakeFiles/icalss-static.dir/icalcalendar.c.o
cd /t
Both python-statsmodels and python2-statsmodels sometimes fail on i686
during the "statsmodels.tsa.tests.test_arima.test_start_params_bug" test
with the error "LinAlgError: SVD did not converge". Here's an excerpt
of one such error:
--8<---cut here---start->8--
The following build of 'bless' on x86_64, the most recent at the time of
this writing, failed by timeout after 1 hour of silence:
http://hydra.gnu.org/build/864760#tabs-buildsteps
Here's the tail of the failed build log:
--8<---cut here---start->8---
startin
In the last three weeks, wireless-regdb has failed to build 4 times on
armhf, although after restarting, the same derivations have later been
built successfully. The last two failures were for the following
derivation, which finally succeeded on the third try:
http://hydra.gnu.org:3000/build/86
In the last month, 'python-statsmodels' has failed its test suite 5
times in the same place:
--8<---cut here---start->8---
statsmodels.regression.tests.test_lme.TestMixedLM.test_r(False, False, 8) ... ok
statsmodels.regression.tests.test_lme.TestMixedLM.test_r(F
On Fri, Dec 04, 2015 at 11:40:35PM +0100, Florian Paul Schmidt wrote:
> Attached is a first stab at fixing this. There are additional options to
> guix-daemons now:
>
> --cache-failures cache build failures
> --cache-hook-failures cache build failures due to hook failures
> (dep
13 matches
Mail list logo
