all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Jaft <jaft.r@outlook.com>
To: "55516@debbugs.gnu.org" <55516@debbugs.gnu.org>,
	Liliana Marie Prikler <liliana.prikler@ist.tugraz.at>
Subject: [bug#55516] [PATCH] gnu: Add quod-libet.
Date: Sun, 22 May 2022 01:27:33 +0000 (UTC)	[thread overview]
Message-ID: <BY5PR07MB7029C38386B5C0DC328E501B99D59@BY5PR07MB7029.namprd07.prod.outlook.com> (raw)
In-Reply-To: <8ddd3999cc2027287027daab64f8e030922c0909.camel@ist.tugraz.at>


> On Thursday, May 19, 2022, 02:58:45 AM CDT, Liliana Marie Prikler <liliana.prikler@ist.tugraz.at> wrote: 
>
>
>
>
>
> The first one is harmless afaik.  The second means it's trying to write
> to $HOME, so you need to (setenv "HOME" (getcwd)) or similar.

I may be out of my depth, sadly; I added your suggestion, which seems to've worked, but it's failing on one of the test files and I can't seem to find anything that actually outputs why:

 > starting phase `check'
> _XSERVTransmkdir: ERROR: euid != 0,directory /tmp/.X11-unix will not be created.
> running "python setup.py" with command "test" and parameters ()
> running test
> ============================= test session starts ==============================
> platform linux -- Python 3.9.9, pytest-6.2.5, py-1.10.0, pluggy-0.13.1
> rootdir: /tmp/guix-build-quod-libet-4.5.0.drv-0/source, configfile: setup.cfg
> collected 4539 items / 1 skipped / 4538 selected
>
> tests/test___init__.py .....                                             [  0%]
> tests/test_appdata_files.py ssss                                         [  0%]
> tests/test_browsers___init__.py .........                                [  0%]
> tests/test_browsers__base.py error: in phase 'check': uncaught exception:
> %exception #<&invoke-error program: "python" arguments: ("-c" "import setuptools, tokenize;__file__='setup.py';f=getattr(tokenize, 'open', open)(__file__);code=f.read().replace('\\r\\n', '\\n');f.close();exec(compile(code, __file__, 'exec'))" "test") exit-status: #f term-signal: 5 stop-signal: #f> 

I tried with ~--keep-failed~ and dug around for logs or something that gave more indication as to why or what in the test file failed but can't seem to find anything. I dunno if you have experience with anything that might lend some insight as to, at least, where to look but, without a better error output, I'm not sure. I tried looking around in the last-listed test file but nothing obvious sticks out to me as would cause an exception, unfortunately.




  reply	other threads:[~2022-05-22  1:28 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-19  4:41 [bug#55516] [PATCH] gnu: Add quod-libet Wamm K. D
2022-05-19  6:15 ` Liliana Marie Prikler
2022-05-19  7:49   ` Jaft
2022-05-19  7:58     ` Liliana Marie Prikler
2022-05-22  1:27       ` Jaft [this message]
2022-05-21 14:45 ` Remco van 't Veer
2022-05-21 14:48   ` [bug#55516] [PATCH] gnu: Add quodlibet Remco van 't Veer
2022-05-27 21:54   ` [bug#55516] [PATCH] gnu: Add quod-libet Ludovic Courtès
2022-05-28  8:55     ` Remco van 't Veer
2022-05-30  2:06       ` Wamm K. D.
2022-05-28  8:57     ` [bug#55516] [PATCH v2] gnu: Add quodlibet Remco van 't Veer
2022-05-28 11:13       ` bug#55516: " Liliana Marie Prikler
2022-05-28 12:36       ` [bug#55516] " Maxime Devos

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=BY5PR07MB7029C38386B5C0DC328E501B99D59@BY5PR07MB7029.namprd07.prod.outlook.com \
    --to=jaft.r@outlook.com \
    --cc=55516@debbugs.gnu.org \
    --cc=liliana.prikler@ist.tugraz.at \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.