Re: Logging testbed started services

[TheJackiMonster]

Thanks,

I found the logs. The only problem was that they got deleted
automatically as soon as the testing system got destroyed. Maybe this
should be configured in the future or depend on the status of the test-
case.

I had to change the flag of the cleanup call in the shutdown_task(...)
of "src/testbed/gnunet-service-testbed.c" manually to GNUNET_NO.

GNUNET_TESTING_system_destroy (GST_context->system, /* GNUNET_YES */
GNUNET_NO);

However new tests won't cleanup logs from old ones. So maybe this work-
around-solution to get the logs isn't great either. Maybe the logs from
services could be redirected/copied to the test-case log or to a sub-
directory. (I won't upload this work-around.)

So I think there are a few points which should be changed when working
on the new test-system for TNG and other parts. If I'm done with the
messenger I will probably look into things to improve in the test-
system.

The messenger seems to work now for multiple peers by the way but I
need more test-cases to be sure. But it could be ready to use and moved
out of experimental in version 0.15.0.

-Jacki

On Sat, 2021-02-06 at 16:55 +0100, Christian Grothoff wrote:
> On 2/6/21 4:50 PM, TheJackiMonster wrote:
> > but I don't
> > get any logs from the services running inside of the testbed.
> > 
> > Is there a way to get those logs?
> 
> Testbed peers should (by default...) log to somewhere in /tmp/.
> Usually,
> the testbed driver creates some unique prefix and then all per-peer
> files are in some sub-directory by number of the peer, i.e. 0/, 1/,
> 2/.
> If you didn't touch the configuration, you should find the logs of
> each
> peer in that subdirectory as well.
> 
> -Christian
>

signature.asc
Description: This is a digitally signed message part