[
https://issues.apache.org/jira/browse/HBASE-12285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14193670#comment-14193670
]
stack commented on HBASE-12285:
-------------------------------
[~dimaspivak] Open a new issue instead?
The surefire snapshot and the culling of the logs put us in a better place for
sure. We have mostly blues now when we build.
We've been failing since #400 because of HBASE-12219. Was this causing the "
There was a timeout or other error in the fork"
Good on you Dima
> Builds are failing, possibly because of SUREFIRE-1091
> -----------------------------------------------------
>
> Key: HBASE-12285
> URL: https://issues.apache.org/jira/browse/HBASE-12285
> Project: HBase
> Issue Type: Bug
> Affects Versions: 1.0.0
> Reporter: Dima Spivak
> Assignee: Dima Spivak
> Priority: Blocker
> Fix For: 2.0.0, 0.99.2
>
> Attachments: HBASE-12285_branch-1_v1.patch,
> HBASE-12285_branch-1_v1.patch
>
>
> Our branch-1 builds on builds.apache.org have been failing in recent days
> after we switched over to an official version of Surefire a few days back
> (HBASE-4955). The version we're using, 2.17, is hit by a bug
> ([SUREFIRE-1091|https://jira.codehaus.org/browse/SUREFIRE-1091]) that results
> in an IOException, which looks like what we're seeing on Jenkins.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
