[System.Runtime.Caching] Make some MemoryCache tests more reliable
authorAlexander Köplinger <alex.koeplinger@outlook.com>
Wed, 4 Mar 2015 21:40:02 +0000 (13:40 -0800)
committerAlexander Köplinger <alex.koeplinger@outlook.com>
Wed, 4 Mar 2015 21:46:04 +0000 (13:46 -0800)
commite5cf24acde3324607611f061e151dbfce80add21
tree1e830264edca308b9dc7305ee1481d9044664b79
parent6fdc2ecf078d5ea557945555fe37bc415936e64f
[System.Runtime.Caching] Make some MemoryCache tests more reliable

After MemoryCache was imported from referencesources, some tests started
failing occasionally. Cross-testing on MS.NET showed that you need to
access the cached item to make MemoryCache.GetCount() reliably return the
correct number after an item was expired from the cache.

Also removed __MonoTimerPeriod and __MonoEmulateOneCPU configuration variables,
they were used in Mono code before and don't make sense with the new code.
mcs/class/System.Runtime.Caching/Test/System.Runtime.Caching/MemoryCacheTest.cs