Kelly,
The test is trivial - three threads try to get the locale data. Before
the fix you'd have multiple threads stomping on each other - after the
fix they should now be synchronized in terms of the primary
initialization. But I'd have to check the actual locale code as that is
where the sy
i have seen a similar bug in my own jprt code where i was accidently working
with HashSet or HashMap objects in two different threads very strange
things like this happened
i dont have the testcase handy to look at but i highly suspect the testcase
this last failure had nothing to with JPRT
On 4/10/2011 3:53 AM, Naoto Sato wrote:
Discussed in the CR 7027061. Never been able to reproduce outside the
JPRT system, and it's difficult to investigate such issue without
reproducing it.
This error message is coming from jtreg:
ACTION: main -- Error. Error while cleaning up threads after
Am 03.10.2011 17:35, schrieb Jason Mehrens:
> What's about moving
>
> public boolean equals(Object o) {return o == this || c.equals(o);}
>
> to CheckedCollection and remove it in CheckedSet (L2394),
CheckedList (L2506)
>
> and
>
> public int hashCode() {return c.hashCode();}
>
> to CheckedColl
Re: In opposition to JEP 103
I oppose the JEP 103 proposal for four major reasons as stated in this PDF:
http://coopsoft.com/dl/Oppose103.pdf
If preferred I can post the text here.
Ed
Discussed in the CR 7027061. Never been able to reproduce outside the
JPRT system, and it's difficult to investigate such issue without
reproducing it.
Naoto
On 10/2/11 7:39 PM, Alan Bateman wrote:
I haven't seen it but Olivier Lagneau asked me off-list recently about
the same issue (same te
> What's about moving
>
> public boolean equals(Object o) {return o == this || c.equals(o);}
>
> to CheckedCollection and remove it in CheckedSet (L2394), CheckedList (L2506)
>
> and
>
> public int hashCode() {return c.hashCode();}
>
> to CheckedCollection and remove it in CheckedSet (L2395)
