retitle 854701 python-asyncssh: FTBFS randomly (failing tests) thanks On Mon, Mar 06, 2017 at 08:52:20PM -0500, Sandro Tosi wrote: > are you still able to reproduce this in your environment?
Yes, I can, but the failure happens randomly. Sorry, I did not know it was random when I initially reported the bug. I just got a lot of failures in a row: Status: failed python-asyncssh_1.8.1-2_amd64-20170201T062219Z Status: failed python-asyncssh_1.8.1-2_amd64-20170204T202532Z Status: failed python-asyncssh_1.8.1-2_amd64-20170209T144310Z Status: failed python-asyncssh_1.8.1-2_amd64-20170209T144312Z Status: failed python-asyncssh_1.8.1-2_amd64-20170209T144938Z Status: failed python-asyncssh_1.8.1-2_amd64-20170209T144936Z Status: failed python-asyncssh_1.8.1-2_amd64-20170209T145601Z Status: failed python-asyncssh_1.8.1-2_amd64-20170209T145603Z Status: failed python-asyncssh_1.8.1-2_amd64-20170209T150235Z Status: failed python-asyncssh_1.8.1-2_amd64-20170209T150241Z Status: failed python-asyncssh_1.8.1-2_amd64-20170209T150909Z Status: failed python-asyncssh_1.8.1-2_amd64-20170209T150920Z Status: failed python-asyncssh_1.8.1-2_amd64-20170209T151555Z Status: failed python-asyncssh_1.8.1-2_amd64-20170209T151602Z Status: failed python-asyncssh_1.8.1-2_amd64-20170209T152235Z Status: failed python-asyncssh_1.8.1-2_amd64-20170209T152247Z Status: failed python-asyncssh_1.8.1-2_amd64-20170209T152902Z Status: failed python-asyncssh_1.8.1-2_amd64-20170209T152921Z Status: failed python-asyncssh_1.8.1-2_amd64-20170209T153532Z Status: failed python-asyncssh_1.8.1-2_amd64-20170209T153554Z Status: failed python-asyncssh_1.8.1-2_amd64-20170209T154154Z Status: failed python-asyncssh_1.8.1-2_amd64-20170209T154230Z Status: failed python-asyncssh_1.8.1-2_amd64-20170209T154818Z Status: failed python-asyncssh_1.8.1-2_amd64-20170209T154854Z Status: failed python-asyncssh_1.8.1-2_amd64-20170209T155446Z Status: failed python-asyncssh_1.8.1-2_amd64-20170209T155528Z Status: failed python-asyncssh_1.8.1-2_amd64-20170209T160131Z Status: failed python-asyncssh_1.8.1-2_amd64-20170209T160213Z and assumed that it would always fail. I'm using retitle to better reflect reality. > i just tried > on an up-to-date pbuilder chroot and it built fine Please try several times (as it happens randomly) using sbuild on a single-cpu system. To double-check, I just build this package today 100 times and it failed 72 times. I'm putting all the build logs here (both successful and failed) for you to see: https://people.debian.org/~sanvila/build-logs/python-asyncssh/ My comments at the end of the initial bug report still holds: * Please try using sbuild on a single-cpu machine. * If you absolutely need it, I could give you access to a machine where this happens (contact me privately for details). Thanks. _______________________________________________ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
