geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kenneth Howe (JIRA)" <j...@apache.org>
Subject [jira] [Created] (GEODE-3980) Windows test failures in AvailablePidTest due to TestTimedOutException in findAvailablePids
Date Tue, 14 Nov 2017 23:02:00 GMT
Kenneth Howe created GEODE-3980:
-----------------------------------

             Summary: Windows test failures in AvailablePidTest  due to TestTimedOutException
in findAvailablePids
                 Key: GEODE-3980
                 URL: https://issues.apache.org/jira/browse/GEODE-3980
             Project: Geode
          Issue Type: Bug
          Components: management
            Reporter: Kenneth Howe


Stack trace from pipeline failure:
{code:title=findAvailablePidsShouldReturnNoDuplicatedPids}
org.junit.runners.model.TestTimedOutException: test timed out after 20 seconds
	at java.io.WinNTFileSystem.list(Native Method)
	at java.io.File.list(File.java:1122)
	at java.io.File.listFiles(File.java:1248)
	at sun.jvmstat.perfdata.monitor.protocol.local.LocalVmManager.activeVms(LocalVmManager.java:186)
	at sun.jvmstat.perfdata.monitor.protocol.local.MonitoredHostProvider.activeVms(MonitoredHostProvider.java:150)
	at sun.tools.attach.HotSpotAttachProvider.listVirtualMachines(HotSpotAttachProvider.java:81)
	at sun.tools.attach.WindowsAttachProvider.listVirtualMachines(WindowsAttachProvider.java:76)
	at com.sun.tools.attach.VirtualMachine.list(VirtualMachine.java:147)
	at org.apache.geode.internal.process.AttachProcessUtils.isProcessAlive(AttachProcessUtils.java:35)
	at org.apache.geode.internal.process.ProcessUtils.isProcessAlive(ProcessUtils.java:81)
	at org.apache.geode.internal.process.lang.AvailablePid.findAvailablePid(AvailablePid.java:131)
	at org.apache.geode.internal.process.lang.AvailablePid.findAvailablePids(AvailablePid.java:148)
	at org.apache.geode.internal.process.lang.AvailablePidTest.findAvailablePidsShouldReturnNoDuplicatedPids(AvailablePidTest.java:109)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
	at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
	at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
	at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
	at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
	at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:298)
	at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:292)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.lang.Thread.run(Thread.java:748)
{code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message