On Mon, 01 Sep 2014, TBB Tests wrote:
Summary
- tor-browser-linux64-3.6.5_ar.tar.xz: failed
- tor-browser-linux64-3.6.5_de.tar.xz: failed
- tor-browser-linux64-3.6.5_en-US.tar.xz: failed
- tor-browser-linux64-3.6.5_es-ES.tar.xz: failed
- tor-browser-linux64-3.6.5_fa.tar.xz: failed
- tor-browser-linux64-3.6.5_fr.tar.xz: failed
- tor-browser-linux64-3.6.5_it.tar.xz: failed
- tor-browser-linux64-3.6.5_ko.tar.xz: failed
- tor-browser-linux64-3.6.5_nl.tar.xz: failed
- tor-browser-linux64-3.6.5_pl.tar.xz: failed
- tor-browser-linux64-3.6.5_pt-PT.tar.xz: failed
- tor-browser-linux64-3.6.5_ru.tar.xz: failed
- tor-browser-linux64-3.6.5_tr.tar.xz: failed
- tor-browser-linux64-3.6.5_vi.tar.xz: failed
- tor-browser-linux64-3.6.5_zh-CN.tar.xz: failed
URL: https://people.torproject.org/~boklm/tbbtests/r/3.6.5-acd36-Fedora20-x86_64/
Test errors
- tor_fte: tor-browser-linux64-3.6.5_ar.tar.xz tor-browser-linux64-3.6.5_de.tar.xz tor-browser-linux64-3.6.5_en-US.tar.xz tor-browser-linux64-3.6.5_es-ES.tar.xz tor-browser-linux64-3.6.5_fa.tar.xz tor-browser-linux64-3.6.5_fr.tar.xz tor-browser-linux64-3.6.5_it.tar.xz tor-browser-linux64-3.6.5_ko.tar.xz tor-browser-linux64-3.6.5_nl.tar.xz tor-browser-linux64-3.6.5_pl.tar.xz tor-browser-linux64-3.6.5_pt-PT.tar.xz tor-browser-linux64-3.6.5_ru.tar.xz tor-browser-linux64-3.6.5_tr.tar.xz tor-browser-linux64-3.6.5_vi.tar.xz tor-browser-linux64-3.6.5_zh-CN.tar.xz - tor_fte_httpproxy: tor-browser-linux64-3.6.5_ar.tar.xz tor-browser-linux64-3.6.5_de.tar.xz tor-browser-linux64-3.6.5_en-US.tar.xz tor-browser-linux64-3.6.5_es-ES.tar.xz tor-browser-linux64-3.6.5_fa.tar.xz tor-browser-linux64-3.6.5_fr.tar.xz tor-browser-linux64-3.6.5_it.tar.xz tor-browser-linux64-3.6.5_ko.tar.xz tor-browser-linux64-3.6.5_nl.tar.xz tor-browser-linux64-3.6.5_pl.tar.xz tor-browser-linux64-3.6.5_pt-PT.tar.xz tor-browser-linux64-3.6.5_ru.tar.xz tor-browser-linux64-3.6.5_tr.tar.xz tor-browser-linux64-3.6.5_vi.tar.xz tor-browser-linux64-3.6.5_zh-CN.tar.xz
Running the tor_fte test on version 3.6.4, we have the same problem.
It seems to be caused by a temporary problem on the fte bridge we are using for the test (128.105.214.162 on port 8080).
I will send an email to Kevin P Dyer about this.