flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-4570) Scalastyle Maven plugin fails undeterministically
Date Fri, 02 Sep 2016 12:56:20 GMT

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

ASF GitHub Bot commented on FLINK-4570:

GitHub user mxm opened a pull request:


    [FLINK-4570] revert Scalastyle version to 0.5.0

    Due to very involved bugs in the 0.8.0 version, we revert back to the 0.5.0 version.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/mxm/flink scalastyle

Alternatively you can review and apply these changes as the patch at:


To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #2462
commit fb88a50315fc5ee5693335edc6bc4d170de8cfe7
Author: Maximilian Michels <mxm@apache.org>
Date:   2016-09-02T12:52:42Z

    [FLINK-4570] revert Scalastyle version to 0.5.0


> Scalastyle Maven plugin fails undeterministically
> -------------------------------------------------
>                 Key: FLINK-4570
>                 URL: https://issues.apache.org/jira/browse/FLINK-4570
>             Project: Flink
>          Issue Type: Bug
>          Components: Build System
>            Reporter: Maximilian Michels
>            Assignee: Maximilian Michels
> The style check fails undeterministically in flink-mesos/src/test/scala/org/apache/flink/mesos/Utils.scala
> It sometimes fails in the nightly builds without any changes to the code which lets the
style check fail. Not reproduceable locally.
> Failed: https://builds.apache.org/job/flink-snapshot-deployment/205/
> Passes: https://builds.apache.org/job/flink-snapshot-deployment/206/
> Failed: https://builds.apache.org/job/flink-snapshot-deployment/207/
> Could be related to upgrading Scalastyle from 0.5.0 to 0.8.0. As a first step, I will
just lower the Scalastyle version to 0.5.0 again.

This message was sent by Atlassian JIRA

View raw message