diff options
author | Tomas Abrahamsson <tomas.abrahamsson@gmail.com> | 2011-12-29 23:38:03 +0100 |
---|---|---|
committer | Tomas Abrahamsson <tomas.abrahamsson@gmail.com> | 2011-12-29 23:38:03 +0100 |
commit | c8f56c7cb239f267a12e86afdfc4b87c9052eba7 (patch) | |
tree | 91ff72d35d82ec13d61206eeffaf1e939947debc /inttest | |
parent | f47d61bc13d4b93c2dc234ceebf27d2d3a18507f (diff) |
Don't kill any inet_gethost_native after eunit
Avoid error reports like this one:
prompt$ rebar eunit
==> dummy (eunit)
Test passed.
=ERROR REPORT==== 29-Dec-2011::23:22:11 ===
** Generic server inet_gethost_native_sup terminating
** Last message in was {'EXIT',<0.62.0>,killed}
** When Server state == {state,inet_gethost_native,undefined,<0.62.0>,
{local,inet_gethost_native_sup}}
** Reason for termination ==
** killed
Previously, it could happen if an eunit test did something that
required a name lookup, like in this example:
-module(dummy_tests).
-include_lib("eunit/include/eunit.hrl").
x_test() ->
{ok, _Hostent} = inet:gethostbyname(localhost).
The inet_gethost_native is a process, started on demand, under a
supervisor_bridge under the kernel_sup, but it is not a gen_server
process or the like, so it has nothing in '$ancestors' in its process
dictionary to indicate it is part of kernel.
Diffstat (limited to 'inttest')
0 files changed, 0 insertions, 0 deletions