GNU bug report logs - #75600
python-pydevd-3.2.3 build failure

Previous Next

Full log

Message #11 received at 75600 <at> debbugs.gnu.org (full text, mbox):

From: "bdju" <bdju <at> tilde.team>
To: "Liliana Marie Prikler" <liliana.prikler <at> gmail.com>,
 <75600 <at> debbugs.gnu.org>
Subject: Re: python-pydevd-3.2.3 build failure
Date: Thu, 16 Jan 2025 04:45:25 -0600

[Message part 1 (text/plain, inline)]

On Thu Jan 16, 2025 at 1:49 AM CST, Liliana Marie Prikler wrote:
> Am Mittwoch, dem 15.01.2025 um 23:26 -0600 schrieb bdju:
> > guix (GNU Guix) 35d13aab7ebca187343c54b800711bfea02859b9
> > Guix System
> > build log attached
> > 
> > ```
> > building /gnu/store/2hpqbgpqkx7zfry7fxz4m1jibbmbppij-python-pydevd-
> > 3.2.3.drv...
> > / 'check' phasebuilder for
> > `/gnu/store/2hpqbgpqkx7zfry7fxz4m1jibbmbppij-python-pydevd-3.2.3.drv'
> > failed with exit code 1
> > […]
> > ```
> > 
> > Most likely related to the font-cozette package by the looks of it.
> font-cozette transitively pulls python-pydevd (you get a similar issue
> with cantarell).  I worked around this locally by building with `-c1'
> to only get one core.  If you were to get the actual build log (e.g.
> with `guix build'), you would likely see that it hits a timeout.
>
> Cheers

Based on what you said, I attempted `guix build --cores=1 font-cozette`,
but it still resulted in a failure. Do I need to just keep trying until
it works or could something else be the problem? Build log attached
again. Should I be build python-pydevd itself instead of font-cozette?
Does that matter for how the core count is applied? I'll try that as
well just in case.

[guix-build-failure_python-pydevd-3.2.3_2.txt (text/plain, attachment)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.