db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-5559) AssertFailures (7, or 8) with ibm 1.6 and 1.5 on Windows XP in lang.NativeAuthProcs fixture testAll
Date Wed, 11 Jan 2012 13:43:39 GMT

    [ https://issues.apache.org/jira/browse/DERBY-5559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13184067#comment-13184067
] 

Rick Hillegas commented on DERBY-5559:
--------------------------------------

Thanks for running these experiments on these platforms, Mike, Myrna, and Kathey. I don't
have these platforms so I can't reproduce the problem you are seeing. I think that increasing
the timeout is the best solution. There are only 2 columns which we can check to verify whether
these procedures ran: HASHINGSCHEME and LASTMODIFIED. The USERNAME column won't change and
the PASSWORD column cannot be inspected via SQL.

When I wrote these tests, the HASHINGSCHEME column was just filled with dummy content. Checking
it would have been useless. Since then, I have wired up password hashing, so HASHINGSCHEME
now contains real content. We can make the value of HASHINGSCHEME change (by changing the
values of the Derby properties which control password hashing behavior). However, I think
the test will give us more confidence that we're testing what we want to (viz, that the procedures
ran) if we don't resort to turning other knobs in order to generate a visible result. I can
look into making that change if the problem is not fixed by increasing the timeout. Sounds
like increasing the timeout is working for you though.

Thanks,
-Rick
                
> AssertFailures (7, or 8) with ibm 1.6 and 1.5 on Windows XP in lang.NativeAuthProcs fixture
testAll
> ---------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-5559
>                 URL: https://issues.apache.org/jira/browse/DERBY-5559
>             Project: Derby
>          Issue Type: Bug
>          Components: Test
>    Affects Versions: 10.9.0.0
>         Environment: Windows XP, IBM 1.6 SR9 FP1, IBM 1.5. SR13
>            Reporter: Myrna van Lunteren
>            Assignee: Mike Matrigali
>         Attachments: derby-5559.diff
>
>
> Since revision 1221569, on windows XP I see some failures in the nightly test like this:
> 1) testAll(org.apache.derbyTesting.functionTests.tests.lang.NativeAuthProcs)junit.framework.AssertionFailedError
> 	at org.apache.derbyTesting.functionTests.tests.lang.NativeAuthProcs.vetResetPassword(NativeAuthProcs.java:364)
> 	at org.apache.derbyTesting.functionTests.tests.lang.NativeAuthProcs.resetPasswordTests(NativeAuthProcs.java:332)
> 	at org.apache.derbyTesting.functionTests.tests.lang.NativeAuthProcs.testAll(NativeAuthProcs.java:189)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
> 	at org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:116)
> 	at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
> 	at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
> 	at junit.extensions.TestSetup.run(TestSetup.java:25)
> 	at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
> 	at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
> 	at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
> 	at junit.extensions.TestSetup.run(TestSetup.java:25)
> 	at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
> 	at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
> 	at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
> 	at junit.extensions.TestSetup.run(TestSetup.java:25)
> 	at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
> 	at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
> 	at junit.extensions.TestSetup.run(TestSetup.java:25)
> 	at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
> 	at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
> 	at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
> 	at junit.extensions.TestSetup.run(TestSetup.java:25)
> 	at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
> 	at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
> 	at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
> 	at junit.extensions.TestSetup.run(TestSetup.java:25)
> 	at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
> 	at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
> 	at junit.extensions.TestSetup.run(TestSetup.java:25)
> See for instance: http://people.apache.org/~myrnavl/derby_test_results/main/windows/testlog/ibm15/1222901-suites.All_diff.txt
> There might be an intermittent issue here, one of the runs lists only 7 failures. But
mostly there's 8.
> This does not occur on Linux with the same jvm versions.
> The changes between this run and the previous one when these failures did not occur:

> ================
> SUBVERSION LOG FROM 1221076 TO 1221569:
> ------------------------------------------------------------------------
> r1221456 | rhillegas | 2011-12-20 11:35:44 -0800 (Tue, 20 Dec 2011) | 1 line
> DERBY-866: Add regression tests for GRANT/REVOKE on new procedures supporting NATIVE
authentication.
> ------------------------------------------------------------------------
> r1221434 | rhillegas | 2011-12-20 10:59:09 -0800 (Tue, 20 Dec 2011) | 1 line
> DERBY-866: Adjust RolesTest to account for new tuple in SYSROUTINEPERMS.
> ------------------------------------------------------------------------
> r1221423 | rhillegas | 2011-12-20 10:44:33 -0800 (Tue, 20 Dec 2011) | 1 line
> DERBY-866: Add syscs_reset_password() and syscs_modify_password() system procedures.
> ================
> derby.log in the failed directory only shows a start and shutdown.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message