Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Winp makes some tests fail on recent Windows versions #2039

Closed
activeeon-bot opened this issue May 19, 2015 · 4 comments
Closed

Winp makes some tests fail on recent Windows versions #2039

activeeon-bot opened this issue May 19, 2015 · 4 comments

Comments

@activeeon-bot
Copy link

Original issue created by Laurent Pellegrino on 19, May 2015 at 14:39 PM - SCHEDULING-2276


Winp makes some tests fail on recent Windows versions (e.g. Windows 8.1 Pro)

@activeeon-bot
Copy link
Author

Original comment posted by Laurent Pellegrino on 20, May 2015 at 11:23 AM


The issue was already reported on the original project but the fix never applied:
https://java.net/jira/browse/WINP-10

I have updated the fix for the current master version and sent a pull-request on the original project:
jenkinsci/winp#20

In the meantime I have pushed our updated version on our nexus repository.

@activeeon-bot
Copy link
Author

Original comment posted by Fabien Viale on 20, May 2015 at 11:26 AM


The error reported during the tests is the following :

(link: Scheduler VM output): java.lang.UnsatisfiedLinkError: Unable to load winp.x64.dll
(link: Scheduler VM output): at org.jvnet.winp.Native.load(Native.java:156)
(link: Scheduler VM output): at org.jvnet.winp.Native.(Native.java:52)
(link: Scheduler VM output): at org.jvnet.winp.WinProcess.enableDebugPrivilege(WinProcess.java:200)
(link: Scheduler VM output): at org.ow2.proactive.rm.util.process.ProcessTreeKiller$Windows.(ProcessTreeKiller.java:245)
(link: Scheduler VM output): at org.ow2.proactive.rm.util.process.ProcessTreeKiller.get(ProcessTreeKiller.java:139)
(link: Scheduler VM output): at org.ow2.proactive.scheduler.task.forked.TaskProcessTreeKiller.kill(TaskProcessTreeKiller.java:61)
(link: Scheduler VM output): at org.ow2.proactive.scheduler.task.nativ.NativeExecutable.execute(NativeExecutable.java:363)
(link: Scheduler VM output): at org.ow2.proactive.scheduler.task.TaskLauncher$ExecutableGuard$9.call(TaskLauncher.java:1926)
(link: Scheduler VM output): at org.ow2.proactive.scheduler.task.TaskLauncher$ExecutableGuard$9.call(TaskLauncher.java:1921)
(link: Scheduler VM output): at org.ow2.proactive.scheduler.task.utils.ActiveObjectExecutor.call(ActiveObjectExecutor.java:102)
(link: Scheduler VM output): at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
(link: Scheduler VM output): at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
(link: Scheduler VM output): at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
(link: Scheduler VM output): at java.lang.reflect.Method.invoke(Method.java:606)
(link: Scheduler VM output): at org.objectweb.proactive.core.mop.MethodCall.execute(MethodCall.java:353)
(link: Scheduler VM output): at org.objectweb.proactive.core.body.request.RequestImpl.serveInternal(RequestImpl.java:214)
(link: Scheduler VM output): at org.objectweb.proactive.core.body.request.RequestImpl.serve(RequestImpl.java:160)
(link: Scheduler VM output): at org.objectweb.proactive.core.body.BodyImpl$ActiveLocalBodyStrategy.serveInternal(BodyImpl.java:552)
(link: Scheduler VM output): at org.objectweb.proactive.core.body.BodyImpl$ActiveLocalBodyStrategy.serve(BodyImpl.java:485)
(link: Scheduler VM output): at org.objectweb.proactive.core.body.AbstractBody.serve(AbstractBody.java:426)
(link: Scheduler VM output): at org.objectweb.proactive.Service.blockingServeOldest(Service.java:206)
(link: Scheduler VM output): at org.objectweb.proactive.Service.blockingServeOldest(Service.java:181)
(link: Scheduler VM output): at org.objectweb.proactive.Service.fifoServing(Service.java:146)
(link: Scheduler VM output): at org.objectweb.proactive.core.body.ActiveBody$FIFORunActive.runActivity(ActiveBody.java:336)
(link: Scheduler VM output): at org.objectweb.proactive.core.body.ActiveBody.run(ActiveBody.java:175)
(link: Scheduler VM output): at java.lang.Thread.run(Thread.java:745)
(link: Scheduler VM output): Caused by: java.lang.UnsatisfiedLinkError: no winp.x64 in java.library.path
(link: Scheduler VM output): at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1886)
(link: Scheduler VM output): at java.lang.Runtime.loadLibrary0(Runtime.java:849)
(link: Scheduler VM output): at java.lang.System.loadLibrary(System.java:1088)
(link: Scheduler VM output): at org.jvnet.winp.Native.load(Native.java:136)
(link: Scheduler VM output): ... 25 more

Even though winp.x64.dll exists (on a Windows 8.1 machine in 64 bits) and is in java.library.path

@activeeon-bot
Copy link
Author

Original comment posted by Laurent Pellegrino on 25, May 2015 at 17:11 PM


Still some issues with some tests such as TestPauseJobRecover on Windows:

(link: 2015-05-25 16:08:23,504 DEBUG) (link: ProcessTreeKiller.hasMatchingEnvVars) Matching Env Var PROCESS_KILLER_COOKIE_TEST , expected: 519c1d0c-c51f-45ca-96e9-6c51c10d7806 found: null
(link: 2015-05-25 16:08:23,506 DEBUG) (link: ProcessTreeKiller$Windows.kill) Analysing process 3028 : (cmd line unacessible)
(link: 2015-05-25 16:08:23,507 DEBUG) (link: ProcessTreeKiller$Windows.kill) Failed to open process error=5 at envvar-cmdline.cpp:86

Fabien, I will send to you a detailed message.

@lpellegr
Copy link
Contributor

lpellegr commented Feb 1, 2016

Linked with #2394.

@lpellegr lpellegr removed this from the 7.X milestone Feb 1, 2016
@fviale fviale closed this as completed Mar 5, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants