[
https://issues.apache.org/jira/browse/OAK-5408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15838136#comment-15838136
]
Francesco Mari edited comment on OAK-5408 at 1/25/17 5:05 PM:
--------------------------------------------------------------
I analyzed the output of the tests in the build 1378. The failures are about
{{o.a.j.o.plugins.segment.standby.BrokenNetworkTest}}, which belongs to
oak-segment. I don't know if it's really worth to debug these tests. First, the
entire code base in oak-segment has been deprecated. Second, we did a huge work
to add stability in the Cold Standby in oak-segment-tar and in the related
tests that consistently improved the stability of the build. This work can't be
trivially ported back to oak-segment. [~mduerig], what to do with the tests for
the Cold Standby implementations in oak-segment? Should they be disabled? Is it
worth to repeat the effort in fixing those tests - and the Cold Standby code -
as we did for oak-segment-tar?
was (Author: frm):
I analyzed the output of the tests in the build 1378. The failures are about
{{o.a.j.o.plugins.segment.standby.BrokenNetworkTest}}, which belongs to
{{oak-segment}}. I don't know if it's really worth to debug these tests. First,
the entire code base in {{oak-segment}} has been deprecated. Second, we did a
huge work to add stability in the Cold Standby in {{oak-segment-tar}} and in
the related tests that consistently improved the stability of the build. This
work can't be trivially ported back to {{oak-segment}}. [~mduerig], what to do
with the tests for the Cold Standby implementations in oak-segment? Should they
be disabled? Is it worth to repeat the effort in fixing those tests - and the
Cold Standby code - as we did for oak-segment-tar?
> Test failure: segment.standby.BrokenNetworkTest
> -----------------------------------------------
>
> Key: OAK-5408
> URL: https://issues.apache.org/jira/browse/OAK-5408
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: continuous integration, tarmk-standby
> Reporter: Hudson
> Assignee: Francesco Mari
> Labels: test-failure
> Fix For: 1.6
>
> Attachments: unit-tests.log
>
>
> Jenkins CI failure:
> https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/
> The build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.7
> (latest),nsfixtures=SEGMENT_MK,profile=unittesting #1355 has failed.
> First failed run: [Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK
> 1.7 (latest),nsfixtures=SEGMENT_MK,profile=unittesting
> #1355|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.7%20(latest),nsfixtures=SEGMENT_MK,profile=unittesting/1355/]
> [console
> log|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.7%20(latest),nsfixtures=SEGMENT_MK,profile=unittesting/1355/console]
> Initially reported test failure: testProxyFlippedStartByte()
> Additional test failure reported via OAK-5476: testProxySSLSkippedBytes()
> Additional test failure reported via OAK-5477: testProxyFlippedStartByteSSL()
> Additional test failures reported via OAK-5478: all tests failed
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
