Am 29.01.2013 um 22:26 schrieb John Sanda:
I got the same exception as Jiri on Mac OS X, b4 bit.
Same here on
snert:/tmp/sigar-procstate-test-master hrupp$ java -version java version "1.7.0_11" Java(TM) SE Runtime Environment (build 1.7.0_11-b21) Java HotSpot(TM) 64-Bit Server VM (build 23.6-b04, mixed mode) snert:/tmp/sigar-procstate-test-master hrupp$ uname -a Darwin snert 11.4.2 Darwin Kernel Version 11.4.2: Thu Aug 23 16:25:48 PDT 2012; root:xnu-1699.32.7~1/RELEASE_X86_64 x86_64
On Jan 29, 2013, at 11:37 AM, Thomas Segismont tsegismo@redhat.com wrote:
Yes the exception you got was what I expected as I see no reason for Linux 32 and 64 bit libs to behave differently.
But why do you say findProcessPid has not find any pid? If it was true you would have seen a RuntimeException "process not found" and not "Expected process to be down at step[0]"
Thomas
Le 29/01/2013 16:54, Jiri Kremser a écrit :
Yes, I was looking into the code. Is my exception the one you were expecting or is it an error in the test? It looks like the findProcessPid() method doesn't find any pid, even If I run the bash-watch-echo.sh script in other terminal.
jk
----- Original Message -----
From: "Thomas Segismont" tsegismo@redhat.com To: rhq-users@lists.fedorahosted.org Sent: Tuesday, January 29, 2013 4:37:27 PM Subject: Re: Sigar getProcState bug on other platforms?
Thanks Jirka. Did you have a look at the test case?
Le 29/01/2013 16:33, Jiri Kremser a écrit :
Hi, I got:
Exception in thread "main" java.lang.RuntimeException: Expected process to be down at step[0] at test.ProcStateTest.testIsRunning(ProcStateTest.java:118) at test.ProcStateTest.main(ProcStateTest.java:29)
on my Fedora17, 32bit (PAE)
Agent and server were down at that moment. JK
----- Original Message -----
From: "Thomas Segismont" tsegismo@redhat.com To: rhq-devel@lists.fedorahosted.org, rhq-users@lists.fedorahosted.org Sent: Monday, January 28, 2013 12:13:17 PM Subject: Sigar getProcState bug on other platforms?
Hi,
Last week I may have found a bug in Sigar[1]. I think it does not only affect Linux amd64 so I ask for your help to determine on which other platforms it may be present.
I pushed a very simple project on GitHub[2]. You can fork it or simply download source zip file.
Then open a terminal, go to the project directory and run: # mvn clean package # java -cp target/sigar/sigar.jar:target/classes/ test/ProcStateTest
If it runs silently then your platform may not be affected. Otherwise, can you send me the error message and your platform type.
Of course if you think it's not a Sigar bug and that I missed something please tell me. I had no response in Sigar user forum so far.
Thanks for your help!
Regards, Thomas
[1] http://communities.vmware.com/message/2183651#2183651 [2] https://github.com/tsegismont/sigar-procstate-test _______________________________________________ rhq-users mailing list rhq-users@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/rhq-users
rhq-users mailing list rhq-users@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/rhq-users
rhq-users mailing list rhq-users@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/rhq-users
rhq-users mailing list rhq-users@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/rhq-users
rhq-users mailing list rhq-users@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/rhq-users
rhq-users mailing list rhq-users@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/rhq-users