[
https://issues.apache.org/jira/browse/LUCENE-7108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15195290#comment-15195290
]
Steve Rowe edited comment on LUCENE-7108 at 3/15/16 1:43 PM:
-------------------------------------------------------------
I didn't try to reproduce, in part because of how long it ran - the last
hearbeat was:
{noformat}
[junit4] HEARTBEAT J3 PID(29575@localhost): 2016-03-14T22:15:10, stalled for
77406s at: Test2BPoints.test2D
{noformat}
I run Lucene-core monster tests via {{ant clean test -Dtests.jvms=4
-Dtests.nightly=true -Dtests.monster=true -Dtests.heapsize=30g}} (via Jenkins's
config). This failing run took 21 hours to complete. I expect it will be
faster next time - this is the first full run since the new monster tests have
run, so the tests' timings will be recorded and should allow the longer-running
ones to be started first.
I had to switch away from my 400GB SSD to a 2TB spinning disk because the first
time I ran the monster tests after the 2B points and BKD monster tests were
added, it ran out of disk space. I checked a couple times when the last two
tests, {{Test2BPoints.test2D()}} and {{Test2BBKDPoints.test2D()}}, were running
on separate JVMs, and the max disk usage I saw was 459GB:
{noformat}
[/slow/jenkins/HDD-workspaces/]$ sudo du -s *
459381964 Lucene-core-nightly-monster-master
{noformat}
was (Author: steve_rowe):
I didn't try to reproduce, in part because of how long it ran - the last
hearbeat was:
{noformat}
[junit4] HEARTBEAT J3 PID(29575@localhost): 2016-03-14T22:15:10, stalled for
77406s at: Test2BPoints.test2D
{noformat}
I run Lucene-core monster tests via {{ant clean test -Dtests.jvms=4
-Dtests.nightly=true -Dtests.monster=true -Dtests.heapsize=30g}} (via Jenkins's
config). This failing run took 21 hours to complete. I expect it will be
faster next time - this is the first full run since the new monster tests'
timings have been recorded.
I had to switch away from my 400GB SSD to a 2TB spinning disk because the first
time I ran the monster tests after the 2B points and BKD monster tests were
added, it ran out of disk space. I checked a couple times when the last two
tests, {{Test2BPoints.test2D()}} and {{Test2BBKDPoints.test2D()}}, were running
on separate JVMs, and the max disk usage I saw was 459GB:
{noformat}
[/slow/jenkins/HDD-workspaces/]$ sudo du -s *
459381964 Lucene-core-nightly-monster-master
{noformat}
> Test2BPoints.test2D() failure
> -----------------------------
>
> Key: LUCENE-7108
> URL: https://issues.apache.org/jira/browse/LUCENE-7108
> Project: Lucene - Core
> Issue Type: Bug
> Reporter: Steve Rowe
>
> From my Jenkins:
> bq. Checking out Revision 3c7e55da3a29224a90a8fc71815a7a52433a6a90
> (refs/remotes/origin/master)
> {noformat}
> [junit4] Suite: org.apache.lucene.index.Test2BPoints
> [junit4] 1> DIR:
> /slow/jenkins/HDD-workspaces/Lucene-core-nightly-monster-master/lucene/build/core/test/J3/temp/lucene.index.Test2BPoints_41B6ADF997AA6777-001/2BPoints1D-001
> [junit4] 1> TEST: now CheckIndex
> [junit4] 2> NOTE: reproduce with: ant test -Dtestcase=Test2BPoints
> -Dtests.method=test2D -Dtests.seed=41B6ADF997AA6777 -Dtests.nightly=true
> -Dtests.slow=true -Dtests.locale=uk-UA -Dtests.timezone=America/Guyana
> -Dtests.asserts=true -Dtests.file.encoding=UTF-8
> [junit4] FAILURE 77421s J3 | Test2BPoints.test2D <<<
> [junit4] > Throwable #1: java.lang.AssertionError: expected:<82595525>
> but was:<0>
> [junit4] > at
> __randomizedtesting.SeedInfo.seed([41B6ADF997AA6777:6C131FA9712D2694]:0)
> [junit4] > at
> org.apache.lucene.index.Test2BPoints.test2D(Test2BPoints.java:137)
> [junit4] > at java.lang.Thread.run(Thread.java:745)
> [junit4] 2> NOTE: leaving temporary files on disk at:
> /slow/jenkins/HDD-workspaces/Lucene-core-nightly-monster-master/lucene/build/core/test/J3/temp/lucene.index.Test2BPoints_41B6ADF997AA6777-001
> [junit4] 2> NOTE: test params are: codec=Asserting(Lucene60): {},
> docValues:{}, maxPointsInLeafNode=1961, maxMBSortInHeap=6.2420286301663985,
> sim=ClassicSimilarity, locale=uk-UA, timezone=America/Guyana
> [junit4] 2> NOTE: Linux 4.1.0-custom2-amd64 amd64/Oracle Corporation
> 1.8.0_45 (64-bit)/cpus=16,threads=1,free=3014352688,total=6316621824
> [junit4] 2> NOTE: All tests run in this JVM: [TestField,
> TestTransactionRollback, TestIndexReaderClose, TestParallelCompositeReader,
> TestCodecs, TestMaxTermFrequency, TestUnicodeUtil, TestMatchNoDocsQuery,
> TestDemoParallelLeafReader, TestStressAdvance, TestFSTs, TestDocIdSetBuilder,
> TestBytesRefHash, TestInfoStream, TestAllFilesDetectTruncation,
> TestForTooMuchCloning, TestNoMergeScheduler, TestRegexpQuery, TestBoostQuery,
> TestPrefixRandom, TestTermsEnum2, TestConsistentFieldNumbers,
> TestExceedMaxTermLength, TestSortRandom, TestReaderClosed, TestSetOnce,
> TestQueryRescorer, TestStressDeletes, TestRecyclingByteBlockAllocator,
> TestSearchAfter, TestBooleanQueryVisitSubscorers, TestOfflineSorter,
> TestReadOnlyIndex, TestLucene50SegmentInfoFormat, TestComplexExplanations,
> TestTopDocsMerge, TestIndexCommit, TestPrefixInBooleanQuery,
> TestSleepingLockWrapper, TestIndexWriterUnicode, TestDirectory,
> TestIndexWriterMerging, Test2BPagedBytes, TestSimilarity2, TestByteBlockPool,
> TestSloppyMath, TestDocCount, TestBinaryDocument, TestSameScoresWithThreads,
> TestScorerPerf, TestScoreCachingWrappingScorer, TestIndexWriter,
> TestPerFieldDocValuesFormat, TestIndexWriterWithThreads,
> TestIndexWriterExceptions, TestMultiMMap, TestBooleanOr, TestBasics,
> TestIndexWriterMergePolicy, TestNRTThreads, MultiCollectorTest,
> TestTermdocPerf, Test2BPositions, TestPackedTokenAttributeImpl,
> TestGrowableByteArrayDataOutput, TestBlockPostingsFormat3,
> TestLucene50CompoundFormat, TestLucene50TermVectorsFormat,
> TestLucene53NormsFormat, TestLucene54DocValuesFormat,
> TestLucene60PointsFormat, TestFieldType, Test2BPoints]
> [junit4] Completed [415/415 (1!)] on J3 in 86675.45s, 2 tests, 1 failure
> <<< FAILURES!
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
