[
https://issues.apache.org/jira/browse/DERBY-2660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12506651
]
Manjula Kutty commented on DERBY-2660:
--------------------------------------
I ran the jdbcapi suite broken in to 4 subsuites and ran them seperately and at
that time there was no hang.
> Problems while running the junit tests on Z series machine
> ----------------------------------------------------------
>
> Key: DERBY-2660
> URL: https://issues.apache.org/jira/browse/DERBY-2660
> Project: Derby
> Issue Type: Test
> Components: Test
> Affects Versions: 10.3.0.0
> Environment: Z series : OS/390
> java:
> java version "1.5.0"
> Java(TM) 2 Runtime Environment, Standard Edition (build pmz31dev-20070201
> (SR4))
> IBM J9 VM (build 2.3, J2RE 1.5.0 IBM J9 2.3 z/OS s390-31 j9vmmz3123-20070201
> (JI
> T enabled)
> J9VM - 20070131_11312_bHdSMr
> JIT - 20070109_1805ifx1_r8
> GC - 200701_09)
> JCL - 20070126
> derby info: 10.3.0.0 alpha - (531672)
> Reporter: Manjula Kutty
> Attachments: derbynet_suite.out, lang_suite.out, tools_suite.out
>
>
> There are quite a few failures and errors but could not figure which tests
> are faling since the stack trace showed only errors for connection problems.
> Then I tried running each suite seperatley. The lang suite ran fine with
> failures for the file comparison tests which uses the LangScripts.java. But
> while running the jdbcapi the tests seems never ending. I tried running the
> tests with the "nohup" command and I could see the java process is still
> running, but no output from the test run other than "....."and occasional FFF
> and EEE. how csould I figure out which test is hanging?? Also Is there a
> better and easy way to get the name of the tests which are passed and which
> are failed???
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
