Probably a spurious failure - I was running rpcrt4 tests on that machine, and they may both have wanted the same port number. Shame on me.
On Fri, Oct 7, 2011 at 12:48 PM, Dan Kegel <[email protected]> wrote: > Fails tests on x86_64? > > On Fri, Oct 7, 2011 at 11:52 AM, <[email protected]> wrote: >> This is an experimental automated build and test service. >> Please feel free to ignore this email while we work the kinks out. >> >> For more info about this message, see http://wiki.winehq.org/BuildBot >> >> The Buildbot has detected a failed build on builder runtests-default-x86_64 >> while building Wine. >> Full details are available at: >> http://buildbot.kegel.com/builders/runtests-default-x86_64/builds/35 (though >> maybe not for long, as I'm still reinstalling the buildbot periodically >> while experimenting) >> BUILD FAILED: failed shell_3 >> >> Errors: >> alarum: failed command was ../../../wine rpcrt4_test.exe.so rpc.c >> fixme:rpc:RpcNetworkIsProtseqValidW Unknown protseq L"foo" >> err:rpc:rpcrt4_protseq_ncacn_ip_tcp_open_endpoint couldn't listen on port >> 4114 >> rpc.c:238: Test failed: RpcServerUseProtseqEp failed (1740) >> fixme:rpc:RpcBindingInqAuthInfoExW authorization service not implemented >> make: *** [rpc.ok] Error 1 >> >> >
