[ovs-dev] Bug#602891: Bug#602891: openvswitch: FTBFS on all arches
Sebastian Andrzej Siewior
sebastian at breakpoint.cc
Tue Nov 9 20:26:25 UTC 2010
* Ben Pfaff | 2010-11-09 09:48:28 [-0800]:
>These tests don't fail for me when I run them locally or on a Debian
>machine (e.g. paganini.debian.org). The testsuite produces more
>information for failed tests, in
>_debian/tests/testsuite.dir/<testnum>/testsuite.log inside the top
>source directory. Is there a way to get this information? Otherwise I
Usually not. The build directory is cleaned after a run. I belive that
there is a switch at sbuild/buildd level to keep the chroot after a
failure but I don't remember it atm.
>am inclined to just disable running the testsutite as part of the Debian
>package build.
You could try to cat some files so they appear in the buildd log on your
next upload.
I just built via
| sbuild --apt-update --batch --dist=unstable --arch=powerpcspe \
| openvswitch_1.1.0~pre2-2
and got the same error message. On buildds it hang in the perl test case
but here it continued. I just tar _my_ folder and it available at [0] in
case it is any help for you.
>From a quick look I see:
|stderr:
| ovsdb-server: failed to chmod control socket
|/build/bigeasy-openvswitch_1.1.0~pre2-2-powerpcspe-T96WR4/openvswitch-1.1.0~pre2/_debian/tests/
|testsuite.dir/022/unixctl (No such file or directory)
and this file does not exist. From a quick look at the source
make_unix_socket() returns non-negative and fails at some point. The
socket name has here ~134 chars. make_sockaddr_un() copies it into a
struct called sockaddr_un which is defined in /usr/include/linux/un.h
as:
| #define UNIX_PATH_MAX 108
|
| struct sockaddr_un {
| sa_family_t sun_family; /* AF_UNIX */
| char sun_path[UNIX_PATH_MAX]; /* pathname */
| };
So I guess that might be it. The functions itself uses a shorter name
but the caller insists on the long one.
Okay. Dinner time.
[0] http://download.breakpoint.cc/openvswitch-1.1.0~pre2.tar.bz2
4b9040f1536364ff06342aa262881e69d6ff868c openvswitch-1.1.0~pre2.tar.bz2
>
>Thanks,
>
>Ben.
Sebastian
More information about the dev
mailing list