aboutsummaryrefslogtreecommitdiffstats
path: root/lib/kernel/test/kernel.spec
diff options
context:
space:
mode:
authorBjörn Gustavsson <[email protected]>2016-03-29 13:30:26 +0200
committerBjörn Gustavsson <[email protected]>2016-03-30 14:29:54 +0200
commit924e9db1d7d51834efdc255893c0d11417def679 (patch)
treea00c87b68ef0c947cbdccb70924ba63a7466464e /lib/kernel/test/kernel.spec
parent272b962f3ddc62f7c67f3558e0f9cd503f920642 (diff)
downloadotp-924e9db1d7d51834efdc255893c0d11417def679.tar.gz
otp-924e9db1d7d51834efdc255893c0d11417def679.tar.bz2
otp-924e9db1d7d51834efdc255893c0d11417def679.zip
gen_fsm_SUITE: Make abnormal1/1 stop failing
abnormal1/1 started failing sporadically when 22785cd1e21 changed using the messages_get/0 and using its own implementation: get_messages() -> receive Msg -> [Msg|get_messages()] after 1 -> [] end. In test_server:messages_get/0, there was "after 0" instead of "after 1" as in this version. We could change back to using "after 0", but it seems that the test case just happened to work before the change. Instead, read out the message that is guranteed to be in the message queue, and *then* check that the message queue is empty.
Diffstat (limited to 'lib/kernel/test/kernel.spec')
0 files changed, 0 insertions, 0 deletions