From: Mariano Lopez <mariano.lopez@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH] sanity.bbclass: Increased verbosity for connectivity check
Date: Mon, 27 Apr 2015 11:12:44 -0500 [thread overview]
Message-ID: <553E5FFC.2030203@linux.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1358 bytes --]
The connectivity sanity error doesn't tell you which URL failed to fetch
nor how it failed.
This provides the URL that failed and why it failed using
BBFetchException messages during the connectivity check.
Please disregard previous patch with the same topic.
[YOCTO #7592]
Signed-off-by: Mariano Lopez <mariano.lopez@linux.intel.com>
---
meta/classes/sanity.bbclass | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/meta/classes/sanity.bbclass b/meta/classes/sanity.bbclass
index cca39c9..f7e8212 100644
--- a/meta/classes/sanity.bbclass
+++ b/meta/classes/sanity.bbclass
@@ -278,12 +278,12 @@ def check_connectivity(d):
try:
fetcher = bb.fetch2.Fetch(test_uris, data)
fetcher.checkstatus()
- except Exception:
+ except Exception as err:
# Allow the message to be configured so that users can be
# pointed to a support mechanism.
msg = data.getVar('CONNECTIVITY_CHECK_MSG', True) or ""
if len(msg) == 0:
- msg = "Failed to fetch test data from the network.
Please ensure your network is configured correctly.\n"
+ msg = '%s. Please ensure your network is configured
correctly.\n' % err
retval = msg
return retval
--
1.8.4.5
[-- Attachment #2: Type: text/html, Size: 2535 bytes --]
next reply other threads:[~2015-04-27 16:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-27 16:12 Mariano Lopez [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-05-13 11:26 [PATCH] sanity.bbclass: Increased verbosity for connectivity check mariano.lopez
2015-04-22 22:17 Mariano Lopez
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=553E5FFC.2030203@linux.intel.com \
--to=mariano.lopez@linux.intel.com \
--cc=openembedded-core@lists.openembedded.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox