river-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Costers (JIRA)" <j...@apache.org>
Subject [jira] Commented: (RIVER-304) Reactivate River jtreg tests
Date Sun, 04 Oct 2009 10:10:56 GMT

    [ https://issues.apache.org/jira/browse/RIVER-304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12762015#action_12762015
] 

Jonathan Costers commented on RIVER-304:
----------------------------------------

OK, a very silly mistake... 
I found a typo in my test.props file: was using jstk instead of jtsk in the jsk.home path
...
That fixes phoenix.jar not being found in above comment (tested running the command manually
as you suggested Peter).

However, I have another question/issue:

In the list of River JARs to be put in jre/lib/ext, I noticed there is no tools.jar mentioned.
If I don't move tools.jar there or add it to jtreg's classpath, I get following output, basically
saying it cannot find ClassServer ...

jonathan@calisto:~/Documenten/NetBeansProjects/River/jtsk/trunk/qa/jtreg$ /home/jonathan/jtreg/linux/bin/jtreg
-verbose:all,nopass -Djsk.home=/home/jonathan/Documenten/NetBeansProjects/River/jtsk/trunk
-dir:/home/jonathan/Documenten/NetBeansProjects/River/jtsk/trunk/qa/jtreg -jdk:/usr/lib/jvm/java-1.5.0-sun
net/jini/activation/Activatable/inactiveGroup
Directory "JTreport" not found: creating
Directory "JTwork" not found: creating
Directory "JTwork/scratch" not found: creating
--------------------------------------------------
TEST: net/jini/activation/Activatable/inactiveGroup/InactiveGroup.java
JDK under test: (/usr/lib/jvm/java-1.5.0-sun)
java version "1.5.0_19"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_19-b02)
Java HotSpot(TM) Server VM (build 1.5.0_19-b02, mixed mode)

ACTION: build -- Passed. Build successful
REASON: User specified action: run build TestLibrary RMID ActivationLibrary 
TIME:   0.995 seconds
messages:
command: build TestLibrary RMID ActivationLibrary
reason: User specified action: run build TestLibrary RMID ActivationLibrary 
elapsed time (seconds): 0.995

ACTION: compile -- Passed. Compilation successful
REASON: .class file out of date or does not exist
TIME:   0.989 seconds
messages:
command: compile /home/jonathan/Documenten/NetBeansProjects/River/jtsk/trunk/qa/jtreg/net/jini/activation/Activatable/inactiveGroup/../../../../../testlibrary/TestLibrary.java
/home/jonathan/Documenten/NetBeansProjects/River/jtsk/trunk/qa/jtreg/net/jini/activation/Activatable/inactiveGroup/../../../../../testlibrary/RMID.java
/home/jonathan/Documenten/NetBeansProjects/River/jtsk/trunk/qa/jtreg/net/jini/activation/Activatable/inactiveGroup/../../../../../testlibrary/ActivationLibrary.java
reason: .class file out of date or does not exist
elapsed time (seconds): 0.989
STDOUT:
STDERR:
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.

ACTION: build -- Passed. Build successful
REASON: User specified action: run build ActivateMe 
TIME:   0.535 seconds
messages:
command: build ActivateMe
reason: User specified action: run build ActivateMe 
elapsed time (seconds): 0.535

ACTION: compile -- Passed. Compilation successful
REASON: .class file out of date or does not exist
TIME:   0.535 seconds
messages:
command: compile /home/jonathan/Documenten/NetBeansProjects/River/jtsk/trunk/qa/jtreg/net/jini/activation/Activatable/inactiveGroup/ActivateMe.java
reason: .class file out of date or does not exist
elapsed time (seconds): 0.535
STDOUT:
STDERR:

ACTION: build -- Passed. Build successful
REASON: User specified action: run build InactiveGroup 
TIME:   0.64 seconds
messages:
command: build InactiveGroup
reason: User specified action: run build InactiveGroup 
elapsed time (seconds): 0.64

ACTION: compile -- Passed. Compilation successful
REASON: .class file out of date or does not exist
TIME:   0.64 seconds
messages:
command: compile /home/jonathan/Documenten/NetBeansProjects/River/jtsk/trunk/qa/jtreg/net/jini/activation/Activatable/inactiveGroup/InactiveGroup.java
reason: .class file out of date or does not exist
elapsed time (seconds): 0.64
STDOUT:
STDERR:

ACTION: build -- Passed. Build successful
REASON: User specified action: run build InactiveGroup_Stub 
TIME:   0.589 seconds
messages:
command: build InactiveGroup_Stub
reason: User specified action: run build InactiveGroup_Stub 
elapsed time (seconds): 0.589

ACTION: compile -- Passed. Compilation successful
REASON: .class file out of date or does not exist
TIME:   0.588 seconds
messages:
command: compile /home/jonathan/Documenten/NetBeansProjects/River/jtsk/trunk/qa/jtreg/net/jini/activation/Activatable/inactiveGroup/InactiveGroup_Stub.java
reason: .class file out of date or does not exist
elapsed time (seconds): 0.588
STDOUT:
STDERR:

ACTION: build -- Passed. All files up to date
REASON: Named class compiled on demand
TIME:   0.0 seconds
messages:
command: build InactiveGroup
reason: Named class compiled on demand
elapsed time (seconds): 0.0

ACTION: main -- Failed. Execution failed: `main' threw exception: TestFailedException: TEST
FAILED: rmid not destroyed in: 60000 milliseconds
REASON: User specified action: run main/othervm/policy=security.policy/timeout=240 -Dtest.rmi.exportType=default
InactiveGroup 
TIME:   5.726 seconds
messages:
command: main  -Dtest.rmi.exportType=defaultInactiveGroup
reason: User specified action: run main/othervm/policy=security.policy/timeout=240 -Dtest.rmi.exportType=default
InactiveGroup 
elapsed time (seconds): 5.726
STDOUT:

Regression test for bug 4116082

STDERR:
exportType: default
HTTPD: using /home/jonathan/Documenten/NetbeansProjects/River/jtsk/trunk/lib/tools.jar on
port 8081 serving /home/jonathan/Documenten/NetbeansProjects/River/jtsk/trunk/lib-dl
TEST FAILED: 
Test failed with: oops
java.io.IOException: oops
	at HTTPD.<init>(HTTPD.java:111)
	at HTTPD.<init>(HTTPD.java:71)
	at RMID.start(RMID.java:184)
	at RMID.start(RMID.java:171)
	at InactiveGroup.main(InactiveGroup.java:107)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at com.sun.javatest.regtest.MainWrapper$MainThread.run(MainWrapper.java:94)
	at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.ClassNotFoundException: com.sun.jini.tool.ClassServer
	at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
	at java.security.AccessController.doPrivileged(Native Method)
	at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
	at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
	at java.lang.Class.forName0(Native Method)
	at java.lang.Class.forName(Class.java:242)
	at HTTPD$Daemon$1.run(HTTPD.java:169)
	at java.security.AccessController.doPrivileged(Native Method)
	at HTTPD$Daemon.create(HTTPD.java:163)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at HTTPD.<init>(HTTPD.java:94)
	... 10 more
ACTIVATION_LIBRARY: tried to shutdown when rmid was not running
TEST FAILED: rmid not destroyed in: 60000 milliseconds
TestFailedException: TEST FAILED: rmid not destroyed in: 60000 milliseconds
	at TestLibrary.bomb(TestLibrary.java:92)
	at TestLibrary.bomb(TestLibrary.java:95)
	at ActivationLibrary.rmidCleanup(ActivationLibrary.java:195)
	at InactiveGroup.main(InactiveGroup.java:188)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at com.sun.javatest.regtest.MainWrapper$MainThread.run(MainWrapper.java:94)
	at java.lang.Thread.run(Thread.java:595)

JavaTest Message: Test threw exception: TestFailedException: TEST FAILED: rmid not destroyed
in: 60000 milliseconds
JavaTest Message: shutting down test

STATUS:Failed.`main' threw exception: TestFailedException: TEST FAILED: rmid not destroyed
in: 60000 milliseconds

TEST RESULT: Failed. Execution failed: `main' threw exception: TestFailedException: TEST FAILED:
rmid not destroyed in: 60000 milliseconds
--------------------------------------------------
Test results: failed: 1
Report written to JTreport/html/report.html
Results written to /home/jonathan/Documenten/NetBeansProjects/River/jtsk/trunk/qa/jtreg/JTwork
Error: Some tests failed or other problems occurred.


Contents of jre/lib/ext:
--------------------------------
jonathan@calisto:~/Documenten/NetBeansProjects/River/jtsk/trunk/qa/jtreg$ ls -al /usr/lib/jvm/java-1.5.0-sun/jre/lib/ext
totaal 2408
drwxr-xr-x  2 root root   4096 2009-10-04 11:53 .
drwxr-xr-x 18 root root   4096 2009-10-01 23:53 ..
-rw-r--r--  1 root root   8215 2009-05-04 12:01 dnsns.jar
-rw-r--r--  1 root root 246722 2009-10-04 11:10 jsk-lib.jar
-rw-r--r--  1 root root 796635 2009-10-04 11:10 jsk-platform.jar
-rw-r--r--  1 root root  24691 2009-10-04 11:10 jsk-policy.jar
-rw-r--r--  1 root root   3939 2009-10-04 11:12 jsk-resources.jar
-rw-r--r--  1 root root 810816 2009-07-15 08:54 localedata.jar
-rw-r--r--  1 root root   2257 2009-10-04 11:10 phoenix-init.jar
-rw-r--r--  1 root root 158419 2009-05-04 11:53 sunjce_provider.jar
-rw-r--r--  1 root root 175949 2009-05-04 11:53 sunpkcs11.jar


If I copy tools.jar into jre/lib/ext, the test passes fine:

jonathan@calisto:~/Documenten/NetBeansProjects/River/jtsk/trunk/qa/jtreg$ /home/jonathan/jtreg/linux/bin/jtreg
-verbose:all,nopass -Djsk.home=/home/jonathan/Documenten/NetBeansProjects/River/jtsk/trunk
-dir:/home/jonathan/Documenten/NetBeansProjects/River/jtsk/trunk/qa/jtreg -jdk:/usr/lib/jvm/java-1.5.0-sun
net/jini/activation/Activatable/inactiveGroup
Directory"JTreport" not found: creating
Directory "JTwork" not found: creating
Directory "JTwork/scratch" not found: creating
Test results: passed: 1
Report written to JTreport/html/report.html
Results written to /home/jonathan/Documenten/NetBeansProjects/River/jtsk/trunk/qa/jtreg/JTwork

Any suggestions?

Thanks
Jonathan

> Reactivate River jtreg tests
> ----------------------------
>
>                 Key: RIVER-304
>                 URL: https://issues.apache.org/jira/browse/RIVER-304
>             Project: River
>          Issue Type: Test
>         Environment: JDK 1.5 or later with jtreg test suite http://www.openjdk.org/jtreg/

>            Reporter: Peter Firmstone
>         Attachments: ant.html, jtreg-output-20090928-JC.tar.gz, jtreg_stdout_errout.txt,
JTreport-jdk1.5-qatests-trunk.tgz, JTreport.tgz, JTwork-jdk5-qatests-trunk.tgz, JTwork.tgz
>
>
> From a recent discussion on river-dev:
> Peter Firmstone wrote:
> > Using the GPLv2 version of jtreg is ok as a platform requirement for the tests,
we just can't distribute it with River.
> >
> > Peter Jones wrote:
> >> On Tue, Apr 21, 2009 at 06:27:18PM +0200, Jonathan Costers wrote:
> >>  
> >>> Something a bit off-topic: the "jtreg tests" are mentioned in the
> >>> discussion you linked to. How do these differ from the other harness/QA
> >>> tests? I must say I haven't really looked at them deeply, but I did
> >>> notice them and that they are separate from the QA suite ...
> >>> For the moment the source just sits there .. Nothing is even compiled.
> >>> Would you be able to give some pointers?
> >>>     
> >>
> >> Sure.  They are written to be run with "jtreg", the test harness used
> >> for regression & unit tests for Sun's JDK.  These days there is a
> >> version of jtreg available under GPLv2 as part of the OpenJDK project,
> >> here:
> >>
> >>     http://www.openjdk.org/jtreg/
> >>
> >> The use of this test framework in addition to the primary Jini QA
> >> framework is historical: some of the APIs added to version 2.0 of the
> >> Jini starter kit-- such as JERI and the related security model,
> >> preferred classes, the configuration stuff-- were originally developed
> >> for the JDK, mostly under JSRs 76 & 78, and thus their implementations
> >> initially had tests written for the jtreg framework.  When those APIs
> >> and implementations were moved to the Jini starter kit, those jtreg
> >> tests came with them, and some new tests in those areas continued to
> >> be added to this jtreg suite.
> >>
> >> The essential jtreg model is very simple: a test is a tagged class
> >> (source file) with a normal "main" method-- if that method completes
> >> normally, the test passes; if it throws an exception (or times out, or
> >> the JVM crashes...), the test fails.  The jtreg goal was to set a very
> >> low barrier to move standalone test cases or example code into the
> >> framework.  The framework does specify more options and nuances, but
> >> it's still pretty simple overall:
> >>
> >>     http://www.openjdk.org/jtreg/tag-spec.txt
> >>
> >> which is quite nice for some things-- of course it doesn't have
> >> anything like the power of the Jini QA framework for testing of
> >> distributed services, etc.  And the Jini jtreg suite has accreted an
> >> unfortunately somewhat ad hoc infrastructure library of its own, in
> >> the "qa/jtreg/testlibrary" directory.  Also, I think that it still has
> >> a few assumptions about being run within Sun's internal network, like
> >> that certain services (a KDC?) are provided by certain host names.
> >>
> >> You just see source files because the harness is responsible for
> >> building them at test execution time.  The jtreg implementation is
> >> built as a layer on top of the JavaTest framework (a much more complex
> >> test framework used for the JCK among other things), which has the
> >> same build-at-test-execution-time model.  (This is nice in that
> >> breaking the compilation of one test doesn't prevent executing other,
> >> unaffected tests-- each test is isolated all the way to its source.)
> >>
> >> I'm not sure how the GPLv2 status of the jtreg implementation
> >> available through the OpenJDK project affects the ability to use it to
> >> run these tests for River.  A nice aspect of the jtreg model's
> >> simplicity is that the test classes themselves do not need to link to
> >> or otherwise refer to any test framework APIs-- there are no such
> >> APIs.  (In theory each of these tests can be run as is, with the right
> >> class paths and javac & java commands.)  At one time the engineering
> >> lead for the Jini QA harness had prototyped adding support for
> >> jtreg-style tests to the Jini harness, and I think that he had gotten
> >> it more or less working, but that effort was dropped for reasons I
> >> can't recall-- although I would guess that it didn't seem like a
> >> priority at the time because jtreg itself was available internally.
> >>
> >> -- Peter
> >>
> >>   

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message