unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: acs@alumni.princeton.edu
Cc: emacs-devel@gnu.org
Subject: Re: 10 unexpected results
Date: Sat, 16 Jan 2021 19:20:33 +0200	[thread overview]
Message-ID: <83zh1894ta.fsf@gnu.org> (raw)
In-Reply-To: <8335z0amsw.fsf@gnu.org> (message from Eli Zaretskii on Sat, 16 Jan 2021 18:06:39 +0200)

> Date: Sat, 16 Jan 2021 18:06:39 +0200
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: emacs-devel@gnu.org
> 
> > 2 unexpected results:
> >    FAILED  bytecomp/warn-obsolete-hook\.el
> >    FAILED  bytecomp/warn-obsolete-variable\.el
> > 
> > 5 unexpected results:
> >    FAILED  xref-elisp-test-find-defs-defgeneric-el
> >    FAILED  xref-elisp-test-find-defs-defun-defvar-el
> >    FAILED  xref-elisp-test-find-defs-defun-el
> >    FAILED  xref-elisp-test-find-defs-defvar-el
> >    FAILED  xref-elisp-test-find-defs-feature-el
> > 
> > 3 unexpected results:
> >    FAILED  xdisp-tests--window-text-pixel-size
> >    FAILED  xdisp-tests--window-text-pixel-size-leading-space
> >    FAILED  xdisp-tests--window-text-pixel-size-trailing-space
> 
> I can only reproduce the last 3, and it's a known problem being worked
> on as we speak.  The other tests all pass for me.  On what OS are you?

Actually, on another system I also see the other ones.  (It's strange
that the problems don't show on mine...)

The bytecomp failures are because the byte-compiler warnings
(sometimes?)  take more than one line, and the regexp there doesn't
match newlines.  I've a fix for that one, which I will install soon
(as soon as Savannah's Git server gets its act together...)

The xref-elisp failures seem to be due to text properties not being
stripped from strings before comparing them?  Can you show the
backtrace of one of these failing tests?



  reply	other threads:[~2021-01-16 17:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-16 15:29 10 unexpected results Vin Shelton
2021-01-16 16:06 ` Eli Zaretskii
2021-01-16 17:20   ` Eli Zaretskii [this message]
2021-01-16 18:12     ` Eli Zaretskii
2021-01-16 18:31       ` Dmitry Gutov
2021-01-16 18:50         ` Eli Zaretskii
2021-01-16 19:39   ` Vin Shelton

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://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=83zh1894ta.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=acs@alumni.princeton.edu \
    --cc=emacs-devel@gnu.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/emacs.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).