.. ====================================================================== ERROR: test_manifest_providers.test_bitbucket ---------------------------------------------------------------------- Traceback (most recent call last): File "/usr/lib64/python2.7/site-packages/nose/case.py", line 197, in runTest ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.0-no-multilib-hardened_libressl-test_20171229-182601 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-7.2.0 * Available Python interpreters, in order of preference: [1] python3.5 [2] python2.7 (fallback) [3] pypy (fallback) java-config: The following VMs are available for generation-2: *) IcedTea JDK 3.6.0 [icedtea-bin-8] Available Java Virtual Machines: [1] icedtea-bin-8 system-vm emerge -qpv dev-python/rosdistro [ebuild N ] dev-python/rosdistro-0.6.3 USE="{-test}" PYTHON_TARGETS="python2_7 python3_5 -pypy -pypy3 -python3_4 -python3_6"
Created attachment 513332 [details] emerge-info.txt
Created attachment 513334 [details] dev-python:rosdistro-0.6.3:20180104-155233.log
Created attachment 513336 [details] emerge-history.txt
Created attachment 513338 [details] environment
Created attachment 513340 [details] etc.portage.tbz2
Created attachment 513342 [details] temp.tbz2
*** Bug 637624 has been marked as a duplicate of this bug. ***
This is a network-sandbox issue. @QA: What is the guideline to handle this ?
Skip tests that require network. You can either inject test runner-specific skip calls/decorators, or prepend '_' to test function names (the latter being easier).
And ofc you can report that upstream and explain to them that depending on random sites working and being accessible all the time is silly, and they should mock stuff or at least provide an easy way to switch those tests off.
(In reply to Michał Górny from comment #9) > Skip tests that require network. You can either inject test runner-specific > skip calls/decorators, or prepend '_' to test function names (the latter > being easier). The whole package is network/random-site-related, RESTRICT=test would have similar effect I fear. I would still like those tests to be ran -- it just allowed me to catch various yaml.load() usages. I was hoping there was a "saner" way to do 'has network-sandbox $FEATURES && skip test' as can be seen in some ebuilds.
Nope, the policy explicitly forbids any kind of network access. You can RESTRICT=test and comment it out when you need to run them locally.
(In reply to Michał Górny from comment #12) > Nope, the policy explicitly forbids any kind of network access. You can > RESTRICT=test and comment it out when you need to run them locally. Fair enough.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=d47dae5503def17a99e7bef777a3b4fceeaf5fe6 commit d47dae5503def17a99e7bef777a3b4fceeaf5fe6 Author: Alexis Ballier <aballier@gentoo.org> AuthorDate: 2019-12-11 15:14:47 +0000 Commit: Alexis Ballier <aballier@gentoo.org> CommitDate: 2019-12-11 15:26:26 +0000 dev-python/rosdistro: disable tests requiring network access Closes: https://bugs.gentoo.org/643458 Package-Manager: Portage-2.3.81, Repoman-2.3.20 Signed-off-by: Alexis Ballier <aballier@gentoo.org> dev-python/rosdistro/rosdistro-0.8.0.ebuild | 6 ++++++ dev-python/rosdistro/rosdistro-9999.ebuild | 7 +++++++ 2 files changed, 13 insertions(+)
