diff options
author | Anders Svensson <[email protected]> | 2017-08-17 00:53:36 +0200 |
---|---|---|
committer | Anders Svensson <[email protected]> | 2017-08-17 12:23:41 +0200 |
commit | d8d3c2a36045bcbe2ae5fd8f08b30a5d103f7bac (patch) | |
tree | 008b27f701680f73d00f7760d0a627212afbbade /lib/diameter/doc/src/diameter.xml | |
parent | a73254692913e689aedf1154c0ee378546502501 (diff) | |
download | otp-d8d3c2a36045bcbe2ae5fd8f08b30a5d103f7bac.tar.gz otp-d8d3c2a36045bcbe2ae5fd8f08b30a5d103f7bac.tar.bz2 otp-d8d3c2a36045bcbe2ae5fd8f08b30a5d103f7bac.zip |
Work around unexpected common_test behaviour
diameter_traffic_SUITE has four layers of nested groups, so when a
testcase is run it should get Config from four init_per_group plus one
init_per_testcase. This isn't what happens: Config is being accumulated
from several init_per_group in some manner that isn't clear, and the
skip in the parent commit somehow results in growing
test_server_gl:init/1 processes that eventually consume all memory.
Replacing rather than prepending to Config in init_per_group works
around this, but the common_test behaviour seems wrong.
Diffstat (limited to 'lib/diameter/doc/src/diameter.xml')
0 files changed, 0 insertions, 0 deletions