unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Wojtek Kosior via "Development of GNU Guix and the GNU System distribution." <guix-devel@gnu.org>
To: "jgart" <jgart@dismail.de>
Cc: guix-devel@gnu.org
Subject: Re: debug moviepy with jgart
Date: Sat, 28 Jan 2023 06:16:42 +0100	[thread overview]
Message-ID: <20230128061642.1ef7790d.koszko@koszko.org> (raw)
In-Reply-To: <ef4f99ca1f648b4752c84f8ab1ef40aa@dismail.de>

[-- Attachment #1: Type: text/plain, Size: 1034 bytes --]

> Hi,
> 
> I'm trying to get the tests to pass for a Guix package that I am writing for moviepy.
> 
> Any thoughts on how to resolve the below failures?
> 
> I need to make some dir writeable?

Hello,

The non-writeable cache dir error seems to be coming from an imagemagick
subprocess. So yeah, we could look at what imagemagick needs for a
cache directory.

There are many errors so I'd try tackling them one by one. Starting
with those that are more obvious to be related to the environment and
IO (and hoping fixing them will also fix some of the non-obvious ones).

You could try using the approach described in [1] to enter the build
environment. Then you can rerun the Hypothesis tests by hand. I'd look
into Hypothesis documentation and check how to only run a sepcific test
to save time. I'd then also check the other options of the tool —
perhaps there's a way to increase verbosity in test output?

Good luck,
Wojtek

[1] https://guix.gnu.org/manual/en/html_node/Debugging-Build-Failures.html

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2023-01-28  5:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-28  4:12 debug moviepy with jgart jgart
2023-01-28  5:16 ` Wojtek Kosior via Development of GNU Guix and the GNU System distribution. [this message]
2023-01-28  6:18 ` jgart

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

  List information: https://guix.gnu.org/

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

  git send-email \
    --in-reply-to=20230128061642.1ef7790d.koszko@koszko.org \
    --to=guix-devel@gnu.org \
    --cc=jgart@dismail.de \
    --cc=koszko@koszko.org \
    /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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).