From: "Ludovic Courtès" <ludo@gnu.org>
To: Brett Gilio <brettg@posteo.net>
Cc: 38325@debbugs.gnu.org
Subject: [bug#38325] [PATCH 1/2] gnu: Add tdlib.
Date: Tue, 26 Nov 2019 21:58:30 +0100 [thread overview]
Message-ID: <87h82qz761.fsf@gnu.org> (raw)
In-Reply-To: <87r21u4emd.fsf@posteo.net> (Brett Gilio's message of "Tue, 26 Nov 2019 13:33:14 -0600")
Hello,
Brett Gilio <brettg@posteo.net> skribis:
> I have fixed the linting issue. The reason why I have disabled tests is
> because the test cases require internet connection.
>
> [ 1][t 0][1574796396.378631592][mtproto.cpp:64][!GetHostByNameActor] 7 "web.telegram.org" [Error : 0 : Failed to resolve host: Name or service not known]
> [ 1][t 0][1574796396.378687382][mtproto.cpp:64][!GetHostByNameActor] 8 "web.telegram.org" [Error : 0 : Failed to resolve host: Name or service not known]
> [ 1][t 0][1574796396.378721476][mtproto.cpp:64][!GetHostByNameActor] 9 "web.telegram.org." [Error : 0 : Failed to resolve host: Name or service not known]
> [ 1][t 0][1574796396.378756762][mtproto.cpp:64][!GetHostByNameActor] 10 "web.telegram.org." [Error : 0 : Failed to resolve host: Name or service not known]
> [ 1][t 0][1574796396.378843307][mtproto.cpp:64][!GetHostByNameActor] 11 "москва.рф" [Error : 0 : Failed to resolve host: Name or service not known]
> [ 1][t 0][1574796396.379258633][mtproto.cpp:64][!GetHostByNameActor] 37 "web.telegram.org" [Error : 0 : Failed to resolve host: Name or service not known]
> [ 1][t 0][1574796396.379312277][mtproto.cpp:64][!GetHostByNameActor] 38 "web.telegram.org" [Error : 0 : Failed to resolve host: Name or service not known]
> [ 1][t 0][1574796396.379376888][mtproto.cpp:64][!GetHostByNameActor] 39 "web.telegram.org." [Error : 0 : Failed to resolve host: Name or service not known]
> [ 1][t 0][1574796396.379430532][mtproto.cpp:64][!GetHostByNameActor] 40 "web.telegram.org." [Error : 0 : Failed to resolve host: Name or service not known]
> [ 1][t 0][1574796396.379479170][mtproto.cpp:64][!GetHostByNameActor] 41 "москва.рф" [Error : 0 : Failed to resolve host: Name or service not known]
> [ 1][t 0][1574796396.381045103][mtproto.cpp:64][!GetHostByNameActor] 67 "web.telegram.org" [Error : 0 : Failed to resolve host: Name or service not known]
> [ 1][t 0][1574796396.381077766][mtproto.cpp:64][!GetHostByNameActor] 68 "web.telegram.org" [Error : 0 : Failed to resolve host: Name or service not known]
> [ 1][t 0][1574796396.381108761][mtproto.cpp:64][!GetHostByNameActor] 69 "web.telegram.org." [Error : 0 : Failed to resolve host: Name or service not known]
> [ 1][t 0][1574796396.381140471][mtproto.cpp:64][!GetHostByNameActor] 70 "web.telegram.org." [Error : 0 : Failed to resolve host: Name or service not known]
> [ 1][t 0][1574796396.381173134][mtproto.cpp:64][!GetHostByNameActor] 71 "москва.рф" [Error : 0 : Failed to resolve host: Name or service not known]
>
> I might be able to strip out those particular tests, but it would seem
> to me that needing internet connection on a test case is likely not the
> "Guix way" of doing this.
Right, there’s no network access in the build environment.
So those tests that rely on being able to talk to telegram.org &
co. must be skipped. If possible, it’s best to skip only those and
still run tests that don’t depend on network access.
If we have to #:tests? #f altogether, then please add a comment
explaining why we’re doing this, for our future selves. :-)
Thanks in advance!
Ludo’.
next prev parent reply other threads:[~2019-11-26 21:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-22 18:55 [bug#38325] [PATCH 1/2] gnu: Add tdlib Brett Gilio
2019-11-26 10:51 ` Ludovic Courtès
2019-11-26 19:33 ` Brett Gilio
2019-11-26 20:58 ` Ludovic Courtès [this message]
2019-11-27 8:09 ` [bug#38325] [PATCH] " Brett Gilio
2019-11-27 8:18 ` Brett Gilio
2019-11-28 19:08 ` Brett Gilio
2019-11-29 13:10 ` bug#38325: " Ludovic Courtès
2019-11-29 19:08 ` [bug#38325] " Brett Gilio
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h82qz761.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=38325@debbugs.gnu.org \
--cc=brettg@posteo.net \
/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/guix.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).