unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Jameson Graef Rollins <jrollins@finestructure.net>
To: David Bremner <david@tethera.net>,
	Daniel Kahn Gillmor <dkg@fifthhorseman.net>,
	notmuch <notmuch@notmuchmail.org>
Subject: Re: fix for failing tests with gmime 2.6.19
Date: Sat, 16 Nov 2013 12:16:23 -0800	[thread overview]
Message-ID: <87iovsxfu0.fsf@servo.finestructure.net> (raw)
In-Reply-To: <87iovzvyui.fsf@zancas.localnet>

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

On Mon, Nov 11 2013, David Bremner <david@tethera.net> wrote:
> David Bremner <david@tethera.net> writes:
>
>> Daniel Kahn Gillmor <dkg@fifthhorseman.net> writes:
>>
>>>
>>> Please don't introduce this cruft into the notmuch codebase.  It should
>>> be fixed in gmime, not worked-around notmuch.
>>>
>>> I've just uploaded gmime 2.6.19-2 to unstable to address this issue.
>>>
>>
>> Hi Daniel;
>>
>> Thanks a lot for that. 
>>
>> What I (still) wonder about is all the people not running Debian, in the
>> interval between the release of notmuch 0.17 and the next upstream
>> release of gmime (and propagation to various distros).  Even on Debian,
>> building on testing and backports complicates things a bit.
>
> An alternative approach would be to fix 
>
>  NOTMUCH_SKIP_TESTS="reply reply-to-sender multipart.37 from-guessing" ./notmuch-test
>
> to return exist status 0, and ideally to print the correct number of
> tests skipped.
>
> I think the former just requires patching line 85 of
> aggregate-results.sh.  I don't see an easy way to do the latter.
>
> This is arguably less crufty, or at least uses existing cruft. On the
> other hand, it doesn't distinguish between a test printing an extra
> space, and complete garbage.

I agree with Daniel that the original series adds a whole lot of
undesirable cruft to the test suite to get around one transient issue in
one of the notmuch dependencies.  That doesn't seem like the best thing
to do imho.  I would vote for this option instead, which doesn't modify
the test suite and just skips the affected tests until the new gmime
versions falls through everywhere.

jamie.

[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]

  reply	other threads:[~2013-11-16 20:16 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-10 16:21 fix for failing tests with gmime 2.6.19 David Bremner
2013-11-10 16:21 ` [PATCH 1/2] test: add optional workaround for gmime bug David Bremner
2013-11-10 16:21 ` [PATCH 2/2] test: work around gmime bug using notmuch_reply_sanitize David Bremner
2013-11-11  3:15   ` [Patch v2 1/2] test: add optional workaround for gmime bug David Bremner
2013-11-11  3:15     ` [Patch v2 2/2] test: work around gmime bug using notmuch_reply_sanitize David Bremner
2013-11-11  3:47 ` fix for failing tests with gmime 2.6.19 Daniel Kahn Gillmor
2013-11-11 11:57   ` David Bremner
2013-11-11 13:42     ` David Bremner
2013-11-16 20:16       ` Jameson Graef Rollins [this message]
2013-11-16 23:00         ` David Bremner
2013-11-11 14:59     ` Tomi Ollila
2013-11-11 16:01       ` Jani Nikula
2013-11-18 17:54 ` Tomi Ollila

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=87iovsxfu0.fsf@servo.finestructure.net \
    --to=jrollins@finestructure.net \
    --cc=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).