unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Tomi Ollila <tomi.ollila@iki.fi>
To: notmuch@notmuchmail.org
Subject: Re: T050-new and T060-count fail if gdb prints a warning
Date: Tue, 10 Mar 2020 21:56:02 +0200	[thread overview]
Message-ID: <m2zhcokmr1.fsf@guru.guru-group.fi> (raw)
In-Reply-To: <87eeu0jjv4.fsf@cgc-instruments.com>

On Tue, Mar 10 2020, Dan Čermák wrote:

> Hi list,
>
> I have encountered a test failure caused by the T050-new and T060-count
> tests in the latest openSUSE-Tumbleweed rebuild with Python 3.8 instead
> of Python 3.7. Both tests die with:
>
> --8<---------------cut here---------------start------------->8---
> T050-new: Testing "notmuch new" in several variations
>  FAIL   Handle files vanishing between scandir and add_file
>        --- T050-new.36.EXPECTED        2020-03-10 12:49:34.388407058 +0000
>        +++ T050-new.36.OUTPUT  2020-03-10 12:49:34.388407058 +0000
>        @@ -1,3 +1,7 @@
>        +/usr/share/gdb/python/gdb/command/prompt.py:48: SyntaxWarning: "is not" with a literal. Did you mean "!="?
>        +  if self.value is not '':
>        +/usr/share/gdb/python/gdb/command/prompt.py:60: SyntaxWarning: "is not" with a literal. Did you mean "!="?
>        +  if self.value is not '':
>         Unexpected error with file /home/abuild/rpmbuild/BUILD/notmuch-0.29.3/test/tmp.T050-new/mail/vanish
>         add_file: Something went wrong trying to read or write a file
>         Error opening /home/abuild/rpmbuild/BUILD/notmuch-0.29.3/test/tmp.T050-new/mail/vanish: No such file or directory
> --8<---------------cut here---------------end--------------->8---
>
> which I think is caused by gdb 8 using some odd Python syntax and is
> completely unrelated to notmuch.
>
> The solution is of course to fix this in gdb (e.g. by updating to gdb
> 9), but the more general question is: can notmuch's testsuite do
> something to avoid issues like this altogether?

setting PYTHONWARNINGS environment variable could probably do it.

IIRC the -count test is something that is harder to replace with
LD_PRELOAD shim...

(btw: thanks for this report -- i learned python3 -bb option
(been hit comparing strings and bytes with == ...) 

>
>
> Cheers,
>
> Dan


Tomi

  parent reply	other threads:[~2020-03-10 19:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-10 15:43 T050-new and T060-count fail if gdb prints a warning Dan Čermák
2020-03-10 16:04 ` David Bremner
2020-03-10 19:56 ` Tomi Ollila [this message]
2020-03-11  9:22   ` Dan Čermák

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=m2zhcokmr1.fsf@guru.guru-group.fi \
    --to=tomi.ollila@iki.fi \
    --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).