On 2014-02-19 09:37, Julian Reschke wrote:
On 2014-02-17 16:49, Michael Dürig wrote:


On 17.2.14 4:41 , Julian Reschke wrote:
On 2014-02-17 16:33, Angela Schreiber wrote:
hm... doesn't fail for me.
as usual: it would be good if you could provide some details if
the problem consistently shows up.
...

What kind of details do you need?


There might be more helpful information in target/unit-tests.log.

Michael

So this problem (or one part of this problem) is caused by the attempt
to use the creation time of the version as key in a sorted map (trying
to sort the history, probably for linear version histories).

This can fail on machines that are sufficiently fast and at the same
time have a > 1ms resolution for systemCurrentTimeMillis (and Date).

In this particular case, the right fix is probably not to attempt to
sort here at all. If it's needed for linear version histories it can be
done somewhere higher by following the successor relation.
...

Turns out that simple versioning already uses a different code path...

Reply via email to