Re: GNUnet build failure on mips64el

[Sree Harsha Totakura]

On 02/22/2014 08:44 AM, Mark H Weaver wrote:
> PASS: test_local_revocation.py
> Feb 22 07:17:50-660583 testbed-api-topology-16547 WARNING Error while 
> establishing a link: 0x4: Timeout while connecting to CORE of peer with id: 0 
> -- Retrying
> Feb 22 07:17:51-098510 testbed-api-topology-16547 WARNING Error while 
> establishing a link: 0x5: Timeout while connecting to CORE of peer with id: 1 
> -- Retrying
> Feb 22 07:17:56-127624 testbed-api-topology-16547 WARNING Error while 
> establishing a link: 0x7: Timeout while acquiring HELLO of peer 6ULB -- 
> Retrying
> Feb 22 07:17:56-134033 testbed-api-topology-16547 WARNING Error while 
> establishing a link: 0x6: Timeout while acquiring HELLO of peer 6DER -- 
> Retrying
> Feb 22 07:18:01-142761 testbed-api-topology-16547 WARNING Error while 
> establishing a link: 0x9: Timeout while acquiring HELLO of peer 6DER -- 
> Retrying
> Feb 22 07:18:01-143920 testbed-api-topology-16547 WARNING Error while 
> establishing a link: 0x8: Timeout while acquiring HELLO of peer 6ULB -- 
> Retrying
> --8<---------------cut here---------------end--------------->8---

These warnings are likely caused due to the system getting overloaded.
The testcase has a test ramp-up part which starts 2 peers and then
connects them.  This part is failing as peers are unable to connect.
> 
> After printing the text above, it gets stuck in
> 'src/revocation/.libs/test_revocation', with the two
> 'gnunet-service-nse' subprocesses both running continuously and all
> other gnunet processes sleeping.

This is likely to cause the load on the system.  'gnunet-service-nse'
tries to find a proof-of-work to participate in the size estimation
application of GNUnet.  This proof-of-work involves find a value whose
hash matches its first n digits; this is required to avoid Sybil attacks
and can be computationally expensive and can be taxing on the loongson
you have.

I am not sure if the NSE service is needed for this testcase.  If not it
should be easy to fix.

In any case, the testcase should not run for more than ~1 minute.  I'd
like to debug this.  Would it be possible to provide me access to this
machine?

Sree