[
https://issues.apache.org/jira/browse/DERBY-6251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13679737#comment-13679737
]
Myrna van Lunteren commented on DERBY-6251:
-------------------------------------------
I've looked at this a bit, because it popped up on a number of branches. As it
started failing after I moved the tests on those branches to new machines (with
a different OS, and on vmware), and there were no relevant changes in derby
code, it seemed indicated that there was something different about those
machine.
Also noteworthy was that the tests didn't fail for 10.8 and 10.5 branches, and
only failed for weme, not any other jvms.
The problem is really that this test did not try to find out the correct
executable. The master shows the test expects to spawn a process using the
executable name 'java'. The executable for weme is 'j9'. The machines where
this passed with weme, had an additional jvm installed in the windows system
directory, so it was actually spawning that. Presumably this was true on the
old machines for the other branches too.
With 10.10 and trunk this has been corrected by converting the test to a junit
test, where it figures out the correct executable.
I have the following options for fixing this:
1) add a jvm to the system path on the machines where this was failing
2) disable the test for weme in all derbyall runs on all branches
3) correct the test, i.e. making it look for the j9 executable if that's the
jvm we're running with, and either add an additional j9 canon to the master
directory and/or add more ignoring code for the _sed.properties file
At this point however, I'm not interested in adding complexity of a proper
check for the older branches and either add, and I prefer to just disable this
test with weme there.
> nightly regression test failure on weme, derbyrunjartest failing with:
> Process exception: (2) The system cannot find the file specified.
> ----------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-6251
> URL: https://issues.apache.org/jira/browse/DERBY-6251
> Project: Derby
> Issue Type: Bug
> Components: Test
> Affects Versions: 10.6.2.3, 10.7.1.4, 10.9.2.2
> Environment: Generating report for RunSuite derbyall j9_foundation11
> j9 null null true
> ------------------ Java Information ------------------
> Java Version: WECE J2ME Foundation Specification v1.1
> Java Vendor: IBM Corporation
> Java home: C:\jartest\weme6.2
> Java classpath:
> C:/jartest/jars/derbyrun.jar;C:/jartest/jars/derbyTesting.jar;c:/jartest/tools/java/jakarta-oro-2.0.8.jar;c:/jartest/junit/junit.jar;
> OS name: Windows Server 2008
> OS architecture: x86
> OS version: 6.1 build 7601 Service Pack 1
> Java user name: cloudtest
> Java user home: C:\Users\cloudtest
> Java user dir: C:\jartest\JarResults.2013-05-17\weme6.2_derbyall
> java.specification.name: J2ME Foundation Specification
> java.specification.version: 1.1
> java.runtime.version: 2.4
> java.fullversion: IBM J9 2.4 Windows Server 2008 x86-32 (JIT enabled, AOT
> enabled)
> J9VM - 20080919_023055_lHdFGQ
> JIT - r9.weme62_20080724_2131
> GC - 20080609_AA
> --------- Derby Information --------
> [C:\jartest\jars\derby.jar] 10.9.2.2 - (1484050)
> [C:\jartest\jars\derbytools.jar] 10.9.2.2 - (1484050)
> [C:\jartest\jars\derbynet.jar] 10.9.2.2 - (1484050)
> [C:\jartest\jars\derbyclient.jar] 10.9.2.2 - (1484050)
> ------------------------------------------------------
> ----------------- Locale Information -----------------
> Current Locale : [English/United States [en_US]]
> Found support for locale: [cs]
> version: 10.9.2.2 - (1484050)
> Found support for locale: [de_DE]
> version: 10.9.2.2 - (1484050)
> Found support for locale: [es]
> version: 10.9.2.2 - (1484050)
> Found support for locale: [fr]
> version: 10.9.2.2 - (1484050)
> Found support for locale: [hu]
> version: 10.9.2.2 - (1484050)
> Found support for locale: [it]
> version: 10.9.2.2 - (1484050)
> Found support for locale: [ja_JP]
> version: 10.9.2.2 - (1484050)
> Found support for locale: [ko_KR]
> version: 10.9.2.2 - (1484050)
> Found support for locale: [pl]
> version: 10.9.2.2 - (1484050)
> Found support for locale: [pt_BR]
> version: 10.9.2.2 - (1484050)
> Found support for locale: [ru]
> version: 10.9.2.2 - (1484050)
> Found support for locale: [zh_CN]
> version: 10.9.2.2 - (1484050)
> Found support for locale: [zh_TW]
> version: 10.9.2.2 - (1484050)
> Reporter: Mike Matrigali
>
> failing consistently on one machine, 10.9, windows, weme -
> http://people.apache.org/~myrnavl/derby_test_results/v10_9/windows/testlog/weme6.2/1484050-derbyall_diff.txt
> *** Start: derbyrunjartest jdkWECE J2ME Foundation Specification v1.1
> derbyall:derbytools 2013-05-17 23:02:07 ***
> 2 del
> < Usage: java org.apache.derby.tools.ij [-p propertyfile] [inputfile]
> 2a2
> > Process exception: (2) The system cannot find the file specified.
> 4 del
> < USAGE: java org.apache.derby.tools.sysinfo -cp [ [ embedded ][ server ][
> client] [ tools ] [ anyClass.class ] ]
> 4a4
> > Process exception: (2) The system cannot find the file specified.
> 6 del
> < USAGE:
> 7 del
> < java org.apache.derby.tools.dblook -d <sourceDBUrl> [OPTIONS]
> 8 del
> < where the source URL is the full URL, including the connection protocol
> 9 del
> < and any connection attributes that might apply. For example, use
> 10 del
> < 'jdbc:derby:myDB', or
> 'jdbc:derby://xxxFILTERED_HOSTNAMExxx:1527/myDB;user=usr;'.
> 11 del
> < options include:
> 12 del
> < -z <schemaName> to specify a schema to which the DDL generation
> 13 del
> < should be limited. Only database objects with that schema will have
> 14 del
> < their DDL generated.
> 15 del
> < -t <tableOne> <tableTwo> ... to specify a list of tables for which
> 16 del
> < the DDL will be generated; any tables not in the list will be ignored.
> 17 del
> < -td <value> to specify what should be appended to the end
> 18 del
> < of each DDL statement.
> 19 del
> < This defaults to ';'.
> 20 del
> < -noview to prevent the generation of DDL for views.
> 21 del
> < -append to keep from overwriting the output files.
> 22 del
> < -verbose to have error messages printed to the console (in addition
> 23 del
> < to the log file). If not specified, errors will only be printed to the
> 24 del
> < log file.
> 25 del
> < -o <filename> to specify the file name to which the generated DDL
> 26 del
> < will be written.
> 27 del
> < If not specified, default is the console.
> 27a6
> > Process exception: (2) The system cannot find the file specified.
> 29 del
> < Usage: NetworkServerControl <commands>
> 30 del
> < Commands:
> 31 del
> < start [-h <host>] [-p <portnumber>] [-noSecurityManager] [-ssl <sslmode>]
> 32 del
> < shutdown [-h <host>][-p <portnumber>] [-ssl <sslmode>] [-user <username>]
> [-password <password>]
> 33 del
> < ping [-h <host>][-p <portnumber>] [-ssl <sslmode>]
> 34 del
> < sysinfo [-h <host>][-p <portnumber>] [-ssl <sslmode>]
> 35 del
> < runtimeinfo [-h <host>][-p <portnumber>] [-ssl <sslmode>]
> 36 del
> < logconnections {on|off} [-h <host>][-p <portnumber>] [-ssl <sslmode>]
> 37 del
> < maxthreads <max>[-h <host>][-p <portnumber>] [-ssl <sslmode>]
> 38 del
> < timeslice <milliseconds>[-h <host>][-p <portnumber>] [-ssl <sslmode>]
> 39 del
> < trace {on|off} [-s <session id>][-h <host>][-p <portnumber>] [-ssl
> <sslmode>]
> 40 del
> < tracedirectory <traceDirectory>[-h <host>][-p <portnumber>] [-ssl <sslmode>]
> 40 add
> > Process exception: (2) The system cannot find the file specified.
> Test Failed.
> *** End: derbyrunjartest jdkWECE J2ME Foundation Specification v1.1
> derbyall:derbytools 2013-05-17 23:02:07 ***
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
