[erlang-questions] CT take a long time to warm up

[Roberto Ostinelli]

Ok,

I finally managed to track this down but I'm totally unsure why this
happens. Motiejus, you were right.

When I run REBAR, the process automountd tries to connect on port 111
(sunrpc) on my local NAT. When it times out, the CT tests are actually run.
If I simply block this process with a firewall, tests start immediately.

I'm at disposal if anyone wants to dig further (tuncer?)

r.

On Wed, Sep 26, 2012 at 1:38 PM, Tuncer Ayaz <tuncer.ayaz@REDACTED> wrote:

> On Wed, Sep 26, 2012 at 9:44 PM, Motiejus Jakštys wrote:
> > On Wed, Sep 26, 2012 at 8:40 PM, Roberto Ostinelli wrote:
> > > > How do you run it? Consistent 20 seconds sounds like a DNS
> > > > timeout issue (stab in the dark).
> > >
> > >
> > > rebar ct_suites=mymodule
> >
> > Hi,
> > adding the list.
> >
> > Please do
> >
> > $TRACE_F rebar ct_suites=mymodule
>
> Make that
>
> $TRACE_F rebar suites=mymodule
>
> and also consider running rebar with fprof:
>
> $TRACE_F rebar -p suites=mymodule
> or
> $TRACE_F rebar --profile suites=mymodule
>
> , but make sure you update rebar first to avoid a faulty
> call to fprof:apply/2.
>
> If it's caused by name lookup, you can try a custom ERL_INETRC file:
> http://www.erlang.org/doc/apps/erts/inet_cfg.html
>
> > and replace $TRACE_F with Max OS C equivalent of "strace -f".
> > Then see what it does just before the 20 second pause.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20121010/93344c9d/attachment.htm>