[
https://issues.apache.org/jira/browse/DERBY-1913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13195151#comment-13195151
]
Mike Matrigali commented on DERBY-1913:
---------------------------------------
failed in nightly's, windows, ibm15, 10.8 branch. This seems to be failing
more often in 10.8 and trunk than other
branches. Maybe there is some unintended interaction with stat background
thread.
http://people.apache.org/~myrnavl/derby_test_results/v10_8/windows/testlog/ibm15/1236501-derbyall_diff.txt
********* Diff file derbyall/storeall/storetests/st_reclaim_longcol.diff
*** Start: st_reclaim_longcol jdk1.5.0 storeall:storetests 2012-01-26 21:47:14
***
1a2,5
> Test 1 failed, expected less than 32 pages - count is:
> free pages : 16
> allocated pages: 20
> Waited 100020ms. for background work.
Test Failed.
*** End: st_reclaim_longcol jdk1.5.0 storeall:storetests 2012-01-26 21:51:27
***
> storetests/st_reclaim_longcol.java fails intermittently
> -------------------------------------------------------
>
> Key: DERBY-1913
> URL: https://issues.apache.org/jira/browse/DERBY-1913
> Project: Derby
> Issue Type: Bug
> Components: Store
> Affects Versions: 10.3.1.4, 10.8.2.3
> Environment: Seen on Solaris 10, 11, jdk1.4, jdk1.5 and jdk 1.6
> Reporter: Knut Anders Hatlen
> Priority: Minor
> Labels: derby_triage10_5_2
>
> I saw this diff when running derbyall:
> ********* Diff file derbyall/storeall/storetests/st_reclaim_longcol.diff
> *** Start: st_reclaim_longcol jdk1.5.0_07 storeall:storetests 2006-10-02
> 18:11:13 ***
> 1a2,4
> > Test failed, expected less than 32 pages - count is:
> > free pages : 25
> > allocated pages: 20
> Test Failed.
> *** End: st_reclaim_longcol jdk1.5.0_07 storeall:storetests 2006-10-02
> 18:13:35 ***
> A similar diff has also been seen in the nightlies:
> http://www.multinet.no/~solberg/public/Apache/DerbyJvm1.4/testlog/SunOS-5.10_i86pc-i386/441833-derbyall_diff.txt
--
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
