Re: [liblo] [ANN] liblo version 0.28 released

On Wed, Feb 5, 2014 at 12:28 PM, Felipe Sateler <fsa...@gm...> wrote:
> On Wed, Feb 5, 2014 at 8:19 AM, Stephen Sinclair <rad...@gm...> wrote:
>> Wait a second.. I've just reviewed the source and the build log in a
>> bit more detail.
>
> For which version? 0.28-1 or 0.28-2?

I hadn't noticed there were multiple versions, but I guess I was
looking at what you linked to before, which seems to be 0.28-2.

>> In server.c, indeed the result of setting SO_REUSEPORT is actually
>> ignored -- and is only tried in a multicast context in any case.
>
> I'm not actually sure about that... that would depend on what does lo_throw do.

You're right, my mistake.  In testlo lo_throw() causes a failure exit.

[... skip ..]

> At the end of the log we see the reason: "Build killed with signal
> TERM after 150 minutes of inactivity". Perhaps testlo is waiting for a
> message that never gets sent? I have to note that the build daemons
> have very restricted internet access so it may well not be possible to
> access the computer itself over the external IP address. This failure
> is different, as the build daemon killed the build after a timeout,
> instead of the build actually failing.

Off the top of my head I can't think why the test would stall for 150
minutes, but perhaps there's an issue.  I thought I'd programmed
testlo with a limited number of tries while waiting for responses from
subtest.  I'll have to take a look.  Hard to debug when I can't
reproduce it though.

(In particular I'm confused by the i386 failure, since I test on my
32-bit laptop all the time. And why is there no x86_64 test?)

> Is it possible to tell testlo to only use localhost? That interface is
> known to be usable for builds.

I'm not sure what the right approach is.  testlo does in principle
depend on a sort of normal networking environment, where it tries to
detect the machine's host address and sends messages back to itself.
Perhaps such tests could be disabled somehow, though currently testlo
and "make test" takes no arguments.  I suppose such a condition could
be specified as an option to configure..

> [1] https://buildd.debian.org/status/logs.php?pkg=liblo

Thanks for this.  It would be great to be able to do such tests on
this Debian system before a release next time.

Steve