[jira] [Commented] (GEODE-219) RegionWithHDFSPersistenceBasicDUnitTest.testGlobalDestroyFromAccessor fails intermittently
[
https://issues.apache.org/jira/browse/GEODE-219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14904919#comment-14904919
]
ASF subversion and git services commented on GEODE-219:
---
Commit 3d648dbf30f3b3d81ee92ae00eb9f23373668f0d in incubator-geode's branch
refs/heads/develop from Ashvin Agrawal
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=3d648db ]
GEODE-219 GEODE-297 GEODE-330: Disable iffy tests
Some HDFS DUnits are not reliable and need to be fixed. Disable them for now to
reduce nightly build noise.
> RegionWithHDFSPersistenceBasicDUnitTest.testGlobalDestroyFromAccessor fails
> intermittently
> --
>
> Key: GEODE-219
> URL: https://issues.apache.org/jira/browse/GEODE-219
> Project: Geode
> Issue Type: Bug
> Components: tests
>Reporter: Dan Smith
>Assignee: Ashvin
> Labels: CI
>
> This test failed in our of our recent jenkins runs
> https://builds.apache.org/job/Geode-nightly/181/testReport/junit/com.gemstone.gemfire.cache.hdfs.internal/RegionWithHDFSOffHeapBasicDUnitTest/testGlobalDestroyFromAccessor/
> {noformat}
> java.lang.AssertionError: Suspicious strings were written to the log during
> this run.
> Fix the strings or use DistributedTestCase.addExpectedException to ignore.
> ---
> Found suspect string in log4j at line 1563
> java.lang.IllegalArgumentException: n must be positive
> {noformat}
> It looks like this test case was added in
> b3e216740d75223252c95c0a016828d63cc13398, assigning to Amogh.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (GEODE-219) RegionWithHDFSPersistenceBasicDUnitTest.testGlobalDestroyFromAccessor fails intermittently
[
https://issues.apache.org/jira/browse/GEODE-219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14900974#comment-14900974
]
Dan Smith commented on GEODE-219:
-
This test just failed again.
https://builds.apache.org/job/Geode-nightly/221/testReport/junit/com.gemstone.gemfire.cache.hdfs.internal/RegionWithHDFSBasicDUnitTest/testGlobalDestroyFromAccessor/
> RegionWithHDFSPersistenceBasicDUnitTest.testGlobalDestroyFromAccessor fails
> intermittently
> --
>
> Key: GEODE-219
> URL: https://issues.apache.org/jira/browse/GEODE-219
> Project: Geode
> Issue Type: Bug
> Components: tests
>Reporter: Dan Smith
>Assignee: Ashvin
> Labels: CI
>
> This test failed in our of our recent jenkins runs
> https://builds.apache.org/job/Geode-nightly/181/testReport/junit/com.gemstone.gemfire.cache.hdfs.internal/RegionWithHDFSOffHeapBasicDUnitTest/testGlobalDestroyFromAccessor/
> {noformat}
> java.lang.AssertionError: Suspicious strings were written to the log during
> this run.
> Fix the strings or use DistributedTestCase.addExpectedException to ignore.
> ---
> Found suspect string in log4j at line 1563
> java.lang.IllegalArgumentException: n must be positive
> {noformat}
> It looks like this test case was added in
> b3e216740d75223252c95c0a016828d63cc13398, assigning to Amogh.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (GEODE-219) RegionWithHDFSPersistenceBasicDUnitTest.testGlobalDestroyFromAccessor fails intermittently
[
https://issues.apache.org/jira/browse/GEODE-219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14900973#comment-14900973
]
Darrel Schneider commented on GEODE-219:
This failed recently:
https://builds.apache.org/job/Geode-nightly/221/testReport/junit/com.gemstone.gemfire.cache.hdfs.internal/RegionWithHDFSBasicDUnitTest/testGlobalDestroyFromAccessor/
The suspect string is a little different:
java.lang.ArrayIndexOutOfBoundsException: 0
> RegionWithHDFSPersistenceBasicDUnitTest.testGlobalDestroyFromAccessor fails
> intermittently
> --
>
> Key: GEODE-219
> URL: https://issues.apache.org/jira/browse/GEODE-219
> Project: Geode
> Issue Type: Bug
> Components: tests
>Reporter: Dan Smith
>Assignee: Amogh Shetkar
> Labels: CI
>
> This test failed in our of our recent jenkins runs
> https://builds.apache.org/job/Geode-nightly/181/testReport/junit/com.gemstone.gemfire.cache.hdfs.internal/RegionWithHDFSOffHeapBasicDUnitTest/testGlobalDestroyFromAccessor/
> {noformat}
> java.lang.AssertionError: Suspicious strings were written to the log during
> this run.
> Fix the strings or use DistributedTestCase.addExpectedException to ignore.
> ---
> Found suspect string in log4j at line 1563
> java.lang.IllegalArgumentException: n must be positive
> {noformat}
> It looks like this test case was added in
> b3e216740d75223252c95c0a016828d63cc13398, assigning to Amogh.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (GEODE-219) RegionWithHDFSPersistenceBasicDUnitTest.testGlobalDestroyFromAccessor fails intermittently
[
https://issues.apache.org/jira/browse/GEODE-219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14711258#comment-14711258
]
Amogh Shetkar commented on GEODE-219:
-
The result location is no longer available, probably not archived. And the
issue is not seen since build #181.
I've been monitoring the nightly build for the issue since then and will
continue to do so for few more days.
> RegionWithHDFSPersistenceBasicDUnitTest.testGlobalDestroyFromAccessor fails
> intermittently
> --
>
> Key: GEODE-219
> URL: https://issues.apache.org/jira/browse/GEODE-219
> Project: Geode
> Issue Type: Bug
> Components: tests
>Reporter: Dan Smith
>Assignee: Amogh Shetkar
>
> This test failed in our of our recent jenkins runs
> https://builds.apache.org/job/Geode-nightly/181/testReport/junit/com.gemstone.gemfire.cache.hdfs.internal/RegionWithHDFSOffHeapBasicDUnitTest/testGlobalDestroyFromAccessor/
> {noformat}
> java.lang.AssertionError: Suspicious strings were written to the log during
> this run.
> Fix the strings or use DistributedTestCase.addExpectedException to ignore.
> ---
> Found suspect string in log4j at line 1563
> java.lang.IllegalArgumentException: n must be positive
> {noformat}
> It looks like this test case was added in
> b3e216740d75223252c95c0a016828d63cc13398, assigning to Amogh.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
