anchor.diff:  %% also a number of other concurrent processes running "nrev" at the same
   %% time. The result is analyzed afterwards by trying to check if the
   %% measured values are reasonable. It is hard to determine what is
  -%% reasonable on different machines therefore the test can sometimes
  -%% fail, even though the timer module is ok. I have checked against
  -%% previous versions of the timer module (which contained bugs) and it
  -%% seems it fails every time when running the buggy timer modules.
  -%% 
  -%% The solution is to rewrite the test suite. Possible strategies for a
  -%% rewrite: smarter math on the measuring data, test cases with varying
  -%% amount of load. The test suite should also include tests that test the
  -%% interface of the timer module.
  +%% reasonable on different machines; therefore the test can sometimes
  +%% fail, even though the timer module is ok.
   
   suite() -> [{ct_hooks,[ts_install_cth]}].
   
  
positive.code: 
  -include_lib("test_server/include/test_server.hrl").
  
  %% Test suite for timer module. This is a really nasty test it runs a
  %% lot of timeouts and then checks in the end if any of them was
  %% trigggered too early or if any late timeouts was much too
  %% late. What should be added is more testing of the interface
  %% functions I guess. But I don't have time for that now.
  %%
  %% Expect it to run for at least 5-10 minutes!
  
  
  %% The main test case in this module is "do_big_test", which
  %% orders a large number of timeouts and measures how
  
negative.code: 
  maybe_start_i_test(Pids, C, 1) ->
      %% ok do it
      TOI = random:uniform(53)*49,
      CountI = random:uniform(10) + 3,                      % at least 4 times
      [spawn_link(timer_SUITE, i_t, [C, TOI, CountI])|Pids];
  maybe_start_i_test(Pids, _C, _) ->
  