s/36
>
>
>
> -Original Message-
> From: Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] On Behalf Of Sven
> Van Caekenberghe
> Sent: Sunday, December 11, 2016 11:56 AM
> To: Pharo Development List
> Subject: Re: [Pharo-dev] NeoUUIDGenerator>>testTwoSam
v [mailto:pharo-dev-boun...@lists.pharo.org] On Behalf Of
> Sven Van Caekenberghe
> Sent: Sunday, December 11, 2016 11:56 AM
> To: Pharo Development List
> Subject: Re: [Pharo-dev] NeoUUIDGenerator>>testTwoSameGenerator -
> intermittent CI failure
>
> Hi Ben,
>
&
r 11, 2016 11:56 AM
> To: Pharo Development List
> Subject: Re: [Pharo-dev] NeoUUIDGenerator>>testTwoSameGenerator -
> intermittent CI failure
>
> Hi Ben,
>
> Thanks for looking into this, it was bothering me for quite some time ;-)
>
> https://pharo.fogbugz.com/f/ca
mailto:pharo-dev-boun...@lists.pharo.org] On Behalf Of Sven
Van Caekenberghe
Sent: Sunday, December 11, 2016 11:56 AM
To: Pharo Development List
Subject: Re: [Pharo-dev] NeoUUIDGenerator>>testTwoSameGenerator - intermittent
CI failure
Hi Ben,
Thanks for looking into this, it was bothering me for
Hi Ben,
Thanks for looking into this, it was bothering me for quite some time ;-)
https://pharo.fogbugz.com/f/cases/19453/NeoUUIDGenerator-testTwoSameGenerator-intermittent-CI-failure
Yes, I think the counter roll-over is the problem, stupid of me to to have seen
this.
The timing problem might
For Case [1] I got an unrelated CI failure [2] for
NeoUUIDGeneratorTests>>#testTwoSameGenerator
Checking this locally by running this a dozen times...
1 to: 1000 do: [:n| last:=n. NeoUUIDGeneratorTests new setUp
testTwoSameGenerator ]
Two distinct failures are apparent...
1. Takes longer than ex
