unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Robert Pluim <rpluim@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Robin Tarsiger <rtt@dasyatidae.com>, emacs-devel@gnu.org
Subject: Re: ai_flags in calls to getaddrinfo, broader call for reproducibility check
Date: Mon, 11 Jan 2021 16:47:29 +0100	[thread overview]
Message-ID: <87o8hvscfi.fsf@gmail.com> (raw)
In-Reply-To: <83eeirfqbo.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 11 Jan 2021 17:25:47 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Robin Tarsiger <rtt@dasyatidae.com>
>> Cc: emacs-devel@gnu.org
>> Date: Mon, 11 Jan 2021 04:47:11 -0600
>> 
>> > Note the difference in he.net resolution with and without the 'ipv6
>> > argument, and also the behavior of ipv6.google.com with the ipv6
>> > argument.  Interesting, no?
>> 
>> Definitely. The behavior of "he.net" with 'ipv6 in the former group
>> is something I think of as to be avoided, per elsethread, but this
>> shows the latter truncation for nil more concretely, of course...
>> and the error-swapping behavior with "ipv6.google.com" is bizarre
>> and hard to reconcile with earlier observations, especially the
>> nil-family case. I wonder whether that changes with 'ipv4?
>
> No, it behaves as expected.
>
>> Your ipconfig result showed no "real" IPv6 connectivity
>
> How did you see this?  Would it be possible to deduce that from the
> output of, say, network-interface-list?
>

You only have fe80 and fec0 addresses listed, which are link-local and
site-local prefixes (and the latter has been deprecated so long itʼs
old enough to drink beer in Belgium)

The only assigned globally routable IPv6 prefix is currently 2000::/3,
so we could check for that via network-interface-list.

> I'm asking because I'm still bothered by failures in those two tests,
> and would like to avoid that.  I think it's bad if a test fails when
> there's nothing wrong with Emacs; we should try to skip such tests
> when we know their results cannot be trusted.

The results can be trusted. However, the assumption of the tests is
that DNS lookups on AAAA records will work, and return results for
google.com, which is not the case for you. If you prefer we can change
the tests to check for "no error" rather than 'returns a result' (is
there an ERT 'should-not-error' clause)?

Robert



  reply	other threads:[~2021-01-11 15:47 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-31 15:06 ai_flags in calls to getaddrinfo Eli Zaretskii
2020-12-31 22:40 ` Robin Tarsiger
2021-01-01  7:43   ` Eli Zaretskii
2021-01-01 11:40     ` Robin Tarsiger
2021-01-01 12:04       ` Robin Tarsiger
2021-01-01 12:48       ` Eli Zaretskii
2021-01-02  0:19         ` Robin Tarsiger
2021-01-03 16:00   ` Eli Zaretskii
2021-01-11 10:47     ` ai_flags in calls to getaddrinfo, broader call for reproducibility check Robin Tarsiger
2021-01-11 12:42       ` Robert Pluim
2021-01-11 15:25       ` Eli Zaretskii
2021-01-11 15:47         ` Robert Pluim [this message]
2021-01-11 16:44           ` Eli Zaretskii
2021-01-11 17:07             ` Robin Tarsiger
2021-01-11 17:53               ` Robert Pluim
2021-01-11 18:30                 ` Robin Tarsiger
2021-01-11 18:42                   ` Robert Pluim
2021-01-11 19:28                     ` Stefan Monnier
2021-01-11 20:12                       ` Robert Pluim
2021-01-11 20:41                         ` Eli Zaretskii
2021-01-11 20:55                           ` Stefan Monnier
2021-01-11 21:02                           ` Robert Pluim
2021-01-11 21:09                             ` Lars Ingebrigtsen
2021-01-11 21:15                               ` Robert Pluim
2021-01-11 22:42                                 ` Lars Ingebrigtsen
2021-01-12  9:40                                   ` Robert Pluim
2021-01-12 12:49                                     ` Lars Ingebrigtsen
2021-01-12 13:04                                       ` Robert Pluim
2021-01-12 14:08                                         ` Lars Ingebrigtsen
2021-01-12 14:29                                           ` Robert Pluim
2021-01-12 18:06                                             ` Lars Ingebrigtsen
2021-01-12 15:14                                       ` Stefan Monnier
2021-01-12 15:45                                         ` Eli Zaretskii
2021-01-12  3:29                             ` Eli Zaretskii
2021-01-11 20:46                 ` Eli Zaretskii
2021-01-11 20:56                   ` Robert Pluim
2021-01-12 15:01                     ` Eli Zaretskii
2021-01-12 15:36                       ` Robert Pluim
2021-01-12 15:42                       ` Eli Zaretskii
2021-01-12 16:00                         ` Robert Pluim
2021-01-12 16:05                           ` Eli Zaretskii
2021-01-12 17:56                             ` Robert Pluim
2021-01-11 19:32           ` Basil L. Contovounesios
2021-01-11 20:19             ` Robert Pluim
2021-01-11 23:57           ` Andy Moreton
2021-01-12  9:44             ` Robert Pluim
2021-01-12 11:56               ` tomas
2021-01-01 10:59 ` ai_flags in calls to getaddrinfo Lars Ingebrigtsen
2021-01-01 12:50   ` Eli Zaretskii
2021-01-02  5:40     ` Lars Ingebrigtsen

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=87o8hvscfi.fsf@gmail.com \
    --to=rpluim@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=rtt@dasyatidae.com \
    /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).