hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dima Spivak (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-12285) Builds are failing, possibly because of SUREFIRE-1091
Date Sat, 18 Oct 2014 06:54:33 GMT

    [ https://issues.apache.org/jira/browse/HBASE-12285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14175892#comment-14175892

Dima Spivak commented on HBASE-12285:

:-( Looks like it failed again, [~stack]. Starting with [#312|https://builds.apache.org/view/H-L/view/HBase/job/HBase-1.0/312/],
the build has failed with console output reading
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.17:test (secondPartTestsExecution)
on project hbase-server: ExecutionException: java.lang.RuntimeException: java.lang.RuntimeException:
java.io.IOException: Stream Closed -> [Help 1]
on about 10 occasions. This seems to be consistent with the Surefire bug, which happens when
a test that writes enough to output to have Surefire switch to a buffer file then tries writing
to stdout during @AfterClass.

The other thing that makes me suspect this is related to the switch of plugins is that the
JIRA notes that "In case of reuseForks=true and forkCount>1, this would even result in
a hanging maven process"; secondPartTestsExecution runs with forks reusing JVMs and with a
fork count of 2, and that's always when Maven dies. Could someone with Jenkins privileges
on builds.apache.org perhaps add {{-e}} to the Maven command being executed so that we can
see a full stack trace if/when this happens again? That'll give us the definitive answer as
to whether this is [SUREFIRE-1091|https://jira.codehaus.org/browse/SUREFIRE-1091] or not.

> 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
> 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

View raw message