[bind10-dev] failed unittests

Thu Mar 29 02:00:40 UTC 2012

Respond two two different threads below:

On Thu, 29 Mar 2012, BIND 10 Tests wrote:

> Subject: failed unittests
> 
> http://git.bind10.isc.org/~tester/builder//BIND10/20120328225844-Debian5Linux-i686/logs/unittests.out
> 
> http://git.bind10.isc.org/~tester/builder//builder.html
> 
> master 34da803fd804c6c0fa7acb90ff46780df69d5898 1332970554
> 
> Last successful master revision (for unittests):
> 6db3556488ae8a75f5250a175f3507cc609ada19
> 
> 
> 1332980102 

On Thu, 29 Mar 2012, BIND 10 Tests wrote:

> Subject: failed test -- master 34da803
> 
> http://git.bind10.isc.org/~tester/2012/03/20120328223624-34da803/make-coverage.out

Two different builds did some related task at the same time; see the 
time stamps:

-rw-r--r-- 1 tester tester 109793 2012-03-29 00:09 
/home/tester/public_html/2012/03/20120328223624-34da803/make-coverage.out

RecursiveQueryTest2.Resolve failure

-rw-r--r-- 1 tester tester 133483 2012-03-29 00:09 
/home/tester/public_html/builder/BIND10/20120328225844-Debian5Linux-i686/logs/unittests.out

IOFetchTest.UdpTimeout failure

I can put some locking in place to prevent this. Or we can consider to 
make sure these use unique ports?

It doesn't happen often so maybe okay to ignore for now.