search

sdslnmd / concurrentlinkedhashmap

Automatically exported from code.google.com/p/concurrentlinkedhashmap
Apache License 2.0
0 stars 0 forks source link

ConcurrentMapTest fails #13

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?

1. Last Changed Rev: 346
2. java version "1.6.0_19"
   Java(TM) SE Runtime Environment (build 1.6.0_19-b04)
   Java HotSpot(TM) 64-Bit Server VM (build 16.2-b04, mixed mode)
   Vista 64-bit dual core
3. ant run-tests

What is the expected output? What do you see instead?

   [testng] ===============================================
   [testng] Ant suite
   [testng] Total tests run: 43, Failures: 1, Skips: 0
   [testng] ===============================================

Please use labels and text to provide additional information.

TestNG files attached.

Original issue reported on code.google.com by zells...@gmail.com on 9 Apr 2010 at 2:08

Attachments:

GoogleCodeExporter commented 9 years ago 
Performing a diff I see a lot of cases like the following. It seems that the 
ordering is not deterministic on your JVM, so entries appear in slightly 
different 
sequences. I think this test of the #toString() which is inherited from 
AbstractMap 
can be removed.

Do you agree?

  923=923
  737=737
  1904=1904
- 2799=2799
  837=837
  1163=1163
  4239=4239
  2818=2818
--- 66,73 ----
  923=923
  737=737
  1904=1904
  837=837
+ 2799=2799
  1163=1163
  4239=4239
  2818=2818

Original comment by Ben.Manes@gmail.com on 9 Apr 2010 at 2:42

GoogleCodeExporter commented 9 years ago 
Agreed, dependency on map ordering can be removed.

Original comment by zells...@gmail.com on 9 Apr 2010 at 3:08

GoogleCodeExporter commented 9 years ago

Original comment by Ben.Manes@gmail.com on 9 Apr 2010 at 3:46