[ovs-dev] Bug#724190: openvswitch: FTBFS: Tests failed

David Suárez david.sephirot at gmail.com
Sun Sep 22 17:08:58 UTC 2013


Source: openvswitch
Version: 1.9.2+git20130813-1
Severity: serious
Tags: jessie sid
User: debian-qa at lists.debian.org
Usertags: qa-ftbfs-20130922 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully): 
> ## ------------- ##
> ## Test results. ##
> ## ------------- ##
> 
> ERROR: 1173 tests were run,
> 10 failed unexpectedly.
> 2 tests were skipped.
> 
> ## ------------------------ ##
> ## Summary of the failures. ##
> ## ------------------------ ##
> Failed tests:
> openvswitch 1.9.2 test suite test groups:
> 
>  NUM: FILE-NAME:LINE     TEST-GROUP-NAME
>       KEYWORDS
> 
>  288: unixctl-py.at:6    unixctl ovs-vswitchd exit - Python
>  289: unixctl-py.at:17   unixctl ovs-vswitchd help - Python
>  290: unixctl-py.at:32   unixctl ovs-vswitchd arguments - Python
>  292: unixctl-py.at:91   unixctl server - Python
>  1152: ovs-monitor-ipsec.at:3 ovs-monitor-ipsec
>  1153: ovs-xapi-sync.at:3 ovs-xapi-sync
>  1172: vlog.at:106        vlog - vlog/reopen - Python
>  1173: vlog.at:135        vlog - vlog/reopen without log file - Python
>  1174: vlog.at:153        vlog - vlog/reopen can't reopen log file - Python
>  1175: vlog.at:185        vlog - vlog/set and vlog/list - Python
> 
> Skipped tests:
> openvswitch 1.9.2 test suite test groups:
> 
>  NUM: FILE-NAME:LINE     TEST-GROUP-NAME
>       KEYWORDS
> 
>  440: timeval.at:3       check that time advances
>       timeval
>  441: timeval.at:8       check that time advances after daemonize()
>       timeval

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2013/09/22/openvswitch_1.9.2+git20130813-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.



More information about the dev mailing list