------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.0-desktop-gnome-systemd_20170619-204631 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-6.3.0 * Available Python interpreters, in order of preference: [1] python3.4 [2] python2.7 (fallback) [3] pypy3 (fallback) [4] jython2.7 (fallback) Available Ruby profiles: [1] ruby21 (with Rubygems) [2] ruby22 (with Rubygems) * java-config: The following VMs are available for generation-2: 1) IcedTea JDK 7.2.6.10 [icedtea-7] 2) IcedTea JDK 7.2.6.10 [icedtea-bin-7] *) IcedTea JDK 3.4.0 [icedtea-bin-8] Available Java Virtual Machines: [1] icedtea-7 [2] icedtea-bin-7 [3] icedtea-bin-8 system-vm
Created attachment 479728 [details] emerge-info.txt
Created attachment 479730 [details] dev-python:fabric-1.12.0:20170701-231727.log
Created attachment 479732 [details] emerge-history.txt
Created attachment 479734 [details] environment
Created attachment 479736 [details] etc.portage.tbz2
Created attachment 479738 [details] temp.tbz2
Created attachment 479740 [details] tests.tbz2
I get the same failure on my machine. It seems to be because upstream requirements paramiko < 2.0 which we don't have in the tree anymore. This makes fabric try to fetch dependencies during tests, generating a sandbox violation. Fabric 1.14 depends on paramiko < 3.0 and runs its tests alright. The solution would then be to stabilize fabric 1.14. Working on this...
Fixed through the stabilization of fabric 1.14