unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: David Bremner <david@tethera.net>
To: Daniel Kahn Gillmor <dkg@fifthhorseman.net>, notmuch@notmuchmail.org
Subject: Re: python-cffi and ruby test suites fail in out-of-tree builds
Date: Thu, 23 Dec 2021 08:57:06 -0400	[thread overview]
Message-ID: <871r23jx7h.fsf@tethera.net> (raw)
In-Reply-To: <87h7w8iwod.fsf@fifthhorseman.net>

Daniel Kahn Gillmor <dkg@fifthhorseman.net> writes:

> Hey folks--
>
> I just did a bit of testing and cleanup for out-of-tree builds (see the
> minor patches that should have landed on the list in the last hour or
> two).
>
> For me, "make check" in an out-of-tree build works fine now, with the
> exception of T391-python-cffi.sh and T395-ruby.sh.
>
> I'm afraid i don't know enough about either python or ruby to see the
> obvious fix for these builds, but i do note that they're the only builds
> which depend on copying their source into the out-of-tree location
> (assuming no one proposes an improvement for
> id:20200522010359.715688-1-dkg@fifthhorseman.net).
>
> Just thought i'd flag this as an outstanding problem that hopefully
> someone clever feels like digging into.

It's a bit of a continual battle to keep the out-of-tree stuff working,
but currently (cea1604a087645d07998c6986a8678b2af239322) this is fixed.

d

      parent reply	other threads:[~2021-12-23 12:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-22  1:29 python-cffi and ruby test suites fail in out-of-tree builds Daniel Kahn Gillmor
2020-05-23 19:52 ` Floris Bruynooghe
2020-05-26 17:08   ` Daniel Kahn Gillmor
2020-05-30 15:48   ` David Bremner
2020-05-26 17:06 ` [PATCH] tests/ruby: Ensure that test works for " Daniel Kahn Gillmor
2020-05-26 17:07   ` Daniel Kahn Gillmor
2020-05-31 19:16   ` David Bremner
2021-12-23 12:57 ` David Bremner [this message]

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://notmuchmail.org/

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

  git send-email \
    --in-reply-to=871r23jx7h.fsf@tethera.net \
    --to=david@tethera.net \
    --cc=dkg@fifthhorseman.net \
    --cc=notmuch@notmuchmail.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://yhetil.org/notmuch.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).