I spotted a problem with data.guix.gnu.org trying to process this old
revision [1]
1: https://data.guix.gnu.org/revision/75dabac633bb9a33efbebf859f8aa4bb3b9582b2
The machine ran out of disk space, as a ~30GiB file had been created in
/var/guix/temproots.
I think I can reproduce the situation by
Hi there!
I pushed a variant of the patch proposed earlier, adding a similar
workaround to ‘Java_java_io_VMFile_exists’ and
‘Java_java_io_VMFile_isDirectory’:
https://git.savannah.gnu.org/cgit/guix.git/commit/?h=core-updates-frozen&id=7f50543d55b20cd528b28d7e15f1bb81001a8da9
With this, I can
Hi Carl,
Carl Dong skribis:
> After resolving bug#49985, a new build failure has stumped a community member
> of mine. When building
> /gnu/store/8kap9kj0ayhaqd4ay7n9lgpbcwankxrq-binutils-mesboot0-2.14.drv, the
> build fails and the logs are as follows:
> https://paste.sr.ht/~dongcarl/7fe559
Hello Guix!
I'm nearly done updating the Rust bootstrap for core-updates-frozen; one
of the changes is that only the current rust (1.54) gets exposed and
used everywhere. This seems to be OK so far, except for mozjs, which
fails to build like so:
--8<---cut here---start--
Hi,
On +2021-09-02 18:41:12 -0400, Simon South wrote:
> Patching strace to add a "--trace-path" parameter to the two tests'
> definitions as in the patch below seems to fix this issue on both
> AArch64 and x86-64, and is less drastic than disabling the tests
> altogether.
>
> The changes limit st
Hi Mathieu,
Mathieu Othacehe writes:
> Hello Maxim,
>
>>> 1. rustc bootstrap from 1.39 (the itch to make it faster comes back
>>> everytime I have to build it ;-)).
>>
>> I'm nearing completion on this front.
>
> That will be a welcomed improvement!
>
>>> 2. fontconfig update that should allow p
Bengt Richter writes:
> A proper configurability, ISTM, would be preferable to any other form
> of more general filtering.
I agree with you on the need to be cautious around modifying test cases
but I'm not sure I follow you otherwise. What would "proper
configurability" look like in this case?
Hi,
Maxim Cournoyer writes:
> Hello Guix!
>
> I'm nearly done updating the Rust bootstrap for core-updates-frozen; one
> of the changes is that only the current rust (1.54) gets exposed and
> used everywhere. This seems to be OK so far, except for mozjs, which
> fails to build like so:
>
> erro
Hi Mathieu,
Mathieu Othacehe writes:
> Hello,
>
> I tried to upgrade glade to the 3.38.2 release on core-update and
> encountered the following test issue:
>
> 2/5 modules FAIL0.29s killed by signal 5 SIGTRAP
GLADE_MODULE_SEARCH_PATH=/home/mathieu/glade-3.38.2/bu
Hi,
python-hy fails to install for me - because there are issues with
python-funcparserlib, as I understand (or tox - cf the end of the log below).
Thanks in advance.
-Andreas
rx@dell ~$ guix package -i python-hy
The following package will be installed:
python-hy 0.18.0
substitute: upd
Hi again,
Maxim Cournoyer writes:
[...]
> Is there a simple reproducer to test my fix? Would just building
> current Glade and its test suite trigger it?
OK, nevermind, I found that the test case was deleting the 'fix-tests'
build phase from glade3, and building the package. I confirm the fi
On +2021-09-03 10:00:33 -0400, Simon South wrote:
> Bengt Richter writes:
> > A proper configurability, ISTM, would be preferable to any other form
> > of more general filtering.
>
> I agree with you on the need to be cautious around modifying test cases
> but I'm not sure I follow you otherwise.
Hello,
I was trying to get a good backtrace for a segfault in linphone-desktop
(see http://issues.guix.gnu.org/47641). So I added a debug output for
liblinphone, and did the following:
--8<---cut here---start->8---
./pre-inst-env guix environment --ad-hoc linp
Hello Maxim,
> OK, nevermind, I found that the test case was deleting the 'fix-tests'
> build phase from glade3, and building the package. I confirm the fix
> works!
Great, that's exactly what I was trying to test but you beat me to it
:). I'll be afk for a month so I won't be able to confirm
Bengt Richter writes:
> Well, that would be the point :)
> I.e., to move the customizations into .conf files and out of
> test-suite sources.
Given the limited flexibility of the test harness I'm not sure there's a
solution that doesn't involve modifying the source, but on reflection
you're right
15 matches
Mail list logo
