Russ Allbery wrote:
> I know you may not be the right person to contact for this.  I'm not sure
> who runs the s390 experimental buildd.  If you're not the right person,
> could you let me know who I should contact (or even better, how I would
> find out such things)?

I am the s390 experimental buildd admin. An approximation of who is, can
be found on experimental.buildd.net. The new wanna build maintainers are
thinking of providing something more suited and more accurate after lenny...

> Luk Claes <l...@debian.org> writes:
> 
>> There was an error while trying to autobuild your package:
>>
>>> Automatic build of remctl_2.13-2 on debian04v1.zseries.org by
>>> sbuild/s390 98-farm Build started at 20081212-1231
>>> Failed Set                 Fail/Total (%) Skip Stat  Failing Tests
>>> -------------------------- -------------- ---- ----  
>>> ------------------------
>>> util/tokens                   1/10    10%    0    0  10
> 
> I suspect there may be an issue with the build host, given that this only
> failed on s390 and this isn't a test that's likely to change with
> different architectures.  The test code in question is checking error
> handling on network sockets by using /dev/full:
> 
>     /* Special test for error handling when sending tokens. */
>     server = open("/dev/full", O_RDWR);
>     if (server < 0)
>         skip(10, "/dev/full not available");
>     else {
>         result.value = xmalloc(5);
>         memcpy(result.value, "hello", 5);
>         result.length = 5;
>         status = token_send(server, 3, &result);
>         free(result.value);
>         ok_int(10, TOKEN_FAIL_SOCKET, status);
>         close(server);
>     }
> 
> If you have a moment, could you try running:
> 
>     ls -l /dev/full

# ls -l /dev/full
crw-rw-rw- 1 root root 1, 5 Sep 15  2006 /dev/full

>     tests/util/tokens-t

2# tests/util/tokens-t
10
ok 1
ok 2
ok 3
ok 4
ok 5
ok 6
ok 7
ok 8
ok 9
not ok 10
  wanted: -2
    seen: 0


> manually in the build tree, which will provide more information about the
> failed test?  I suspect that /dev/full may be a regular file on that host
> or some similar sort of problem has happened.

Pasted inline above...

Cheers

Luk



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to