You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by "Martin van den Bemt (JIRA)" <ji...@apache.org> on 2006/07/05 15:01:30 UTC

[jira] Commented: (SANDBOX-71) [id] Sporadic test failures in TimeBasesAlphanumericIdentifierGeneratorTest

    [ http://issues.apache.org/jira/browse/SANDBOX-71?page=comments#action_12419269 ] 

Martin van den Bemt commented on SANDBOX-71:
--------------------------------------------

Maybe this is some interesting story : http://www.wmware.com/psf/vmware_timekeeping.pdf (If I am not mistaking we (ehh gump) are running on vmware and not on solaris zones (else this doc is pretty much useless). Gump runs on debian btw.
In short  : a kernel option : clock=pit  and in the vmx file the setting tools.syncTime=true (fixed our timing problems on some vmware servers.)
Maybe pining infrastructure to see if this is an option that they can set ?

> [id] Sporadic test failures in TimeBasesAlphanumericIdentifierGeneratorTest
> ---------------------------------------------------------------------------
>
>          Key: SANDBOX-71
>          URL: http://issues.apache.org/jira/browse/SANDBOX-71
>      Project: Commons Sandbox
>         Type: Bug

>   Components: Id
>  Environment: Operating System: other
> Platform: All
>     Reporter: Joerg Schaible
>     Assignee: Joerg Schaible
>  Attachments: TimeBasedAIGTest.patch
>
> The unit tests for TimeBasesAlphanumericIdentifierGenerator fail with Gump
> sometimes for unknown reason. Unfortunately it seems, that the exactly test
> reports are unavailable. Nevertheless I suspect timing problems that interfere
> and may fail running the fixtures of the test within the same time slice.
> Therefore was in setUp() a sleep(50) call that might fail to create a unique
> operation environment for each test fixture depending on the OS/hardware
> environment. This "synchronization" has been replaced with an explicit loop
> waiting for the next time slice.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org