[erlang-questions] CT take a long time to warm up
Thu Oct 11 10:45:11 CEST 2012
Whoa, this is fascinating Roberto. Did you try running common test from the shell by hand and see if it still happens, i.e., by running something like this:
Does the same thing happen?
On 11 Oct 2012, at 04:38, Roberto Ostinelli wrote:
> 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?)
> On Wed, Sep 26, 2012 at 1:38 PM, Tuncer Ayaz <> 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
> $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:
> > and replace $TRACE_F with Max OS C equivalent of "strace -f".
> > Then see what it does just before the 20 second pause.
> erlang-questions mailing list
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 235 bytes
Desc: Message signed with OpenPGP using GPGMail
More information about the erlang-questions