aboutsummaryrefslogtreecommitdiffstats
path: root/lib/dialyzer/README
diff options
context:
space:
mode:
authorMicael Karlberg <[email protected]>2014-03-14 18:41:23 +0100
committerMicael Karlberg <[email protected]>2014-03-14 18:41:23 +0100
commit3e8aa3462a151d6b528bab917bfa7b4aab021ba5 (patch)
treed91c15a73ba74299c7d9e6675e534ece9464edd6 /lib/dialyzer/README
parentbcfc2e4770123f067c346d96b11d9382ff2b6bcc (diff)
downloadotp-3e8aa3462a151d6b528bab917bfa7b4aab021ba5.tar.gz
otp-3e8aa3462a151d6b528bab917bfa7b4aab021ba5.tar.bz2
otp-3e8aa3462a151d6b528bab917bfa7b4aab021ba5.zip
[snmp/agent] Fixed request id generation
When testing the agent, it is started and then used for a series (v1, v2, v3, ...) of tests. But the individual test cases are use one instance of the test manager. Because of this, the requerst id cannot be a counter starting from 1 or any counter for that matter. Instead every request id was generated using random. But this is obiously not a guarantee fo uniqueness, it merely makes it unlikely that the request ids will be reused. To get around this problem (without having to rewrite the entire agent test suite) a simple (global) counter server is introduced. It is started at the start of the agent test suite (init_per_suite) and stopped at the end (end_per_suite).
Diffstat (limited to 'lib/dialyzer/README')
0 files changed, 0 insertions, 0 deletions