On Sat, Oct 08, 2016 at 07:27:08PM +0200, Danny Milosavljevic wrote:
> > Also if guix build does fail executing some test - can I continue there
> > somehow?
>
> Uhhh... I mean: if a test fails, can I make guix open a shell there (with all
> the right environment etc) so I can examine what's
> Also if guix build does fail executing some test - can I continue there
> somehow?
Uhhh... I mean: if a test fails, can I make guix open a shell there (with all
the right environment etc) so I can examine what's up, let me fix it and then
restart the phase?
and the patch...
--- /tmp/sysconfig_pypy.py 2016-09-14 00:38:36.325334296 +0200
+++ pypy3.3-v5.2.0-alpha1-src/lib-python/3/distutils/sysconfig_pypy.py 2016-09-14 00:37:55.068908258 +0200
@@ -123,6 +123,19 @@
optional C speedup components.
"""
if compiler.compiler_type == "unix":
+
Hi,
here's a work-in-progress package for pypy3.3. It builds - but the tests fail.
A build takes about 6 GB of RAM and about 9 hours.
Maybe someone can spot how to fix one of the tests (usually they don't find
libraries etc). (I'll work it out eventually but I thought I'd ask)
Also if guix
