Re: Bug#306711: Current buildd output/logs
On Fri, Apr 29, 2005 at 10:12:25AM +0200, Peter Van Eynde wrote:
> I found the problem: during the build the system does a self-test that uses
> /dev/log, this fails with a connection refused:
>
> Test SB-BSD-SOCKETS-TEST::SIMPLE-LOCAL-CLIENT failed
> Form: (PROGN
> (WHEN
> (AND (PROBE-FILE "/dev/log")
> (SB-POSIX:S-ISSOCK
> (SB-POSIX:STAT-MODE (SB-POSIX:STAT "/dev/log"))))
> ...
> (FORMAT STREAM
> "<7>bsd-sockets: Don't panic. We're testing
> local-domain client code; this message can safely be ignored"))))
> T)
> Expected value: T
> Actual value: #<SB-BSD-SOCKETS:CONNECTION-REFUSED-ERROR {10011C4841}>.
>
> I have no idea how to write a build-depends on a /dev/log file. Nor for
> that matter on a working TCP/UDP echo service needed for another test.
Maybe packages shouldn't assume they can do such tests and just don't
bother. Why would the buildd admin want to allow the buildd to put crap
in their log files of the system? Seems like a bad idea to me.
Do these tests actually pass when run on other architectures' buildds?
Len Sorensen
Reply to: