History item is not kept while module compiler is running

[luos]

History item is not kept while module compiler is running

[eproxus]

Finally got around to looking at this today. I couldn't reproduce it with the simple test on my (faster?) machine, so I had to create this monster version:

-module(mt_reload_test).
-include_lib("eunit/include/eunit.hrl").

-compile(export_all).

proc_fn() ->
    receive
        {do_call, Arg} ->
            ?debugFmt("[~p] called: ~p~n", [self(), mt_app:test_fn(Arg)])
    end,
    proc_fn().

reload_test() ->
    Proc = spawn(fun proc_fn/0),
    meck:new(mt_app, [passtrough]),
    meck:expect(mt_app, test_fn, fun(Arg) -> {mocked, Arg} end),
    spawn(fun() ->
            lists:map(fun(N) ->
                        timer:sleep(1),
                        Proc ! {do_call, N}
                     end, lists:seq(0, 800))
          end),
    [meck:expect(mt_app, test_fn, fun(Arg) -> {mocked2, Arg} end) || _ <- lists:seq(1, 5)],

    timer:sleep(4500),
    ?debugFmt("History: ~p~n",[meck:history(mt_app)]),
    ?assertEqual(801, meck:num_calls(mt_app, test_fn, '_'))
    .

I'm also not sure why the reload case is there, and why we don't store history while reloading is active (history is historical, so it should be stored regardless I think). By removing it, this test passes and it doesn't seem to break any other tests.

[luos]

Hi,

Thanks for checking and for the fix!

[eproxus]

@luos Thanks for reporting it and providing a base test case, very much appreciated!