[
https://issues.apache.org/jira/browse/NIFI-2728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15463106#comment-15463106
]
ASF GitHub Bot commented on NIFI-2728:
--------------------------------------
Github user apiri commented on the issue:
https://github.com/apache/nifi/pull/985
Seems fair, although I would almost prefer that the two items get flipped
in terms of testing. Always run contrib check (without tests) during the build
and then run the full test suite. In the linked build, it seems the tests
failure from the environment seemingly prevented the contrib check from
running, which, as a reviewer, is typically the most time consuming part of the
review process.
Thoughts?
> Travis CI experiences GC overhead limit exceeded
> -------------------------------------------------
>
> Key: NIFI-2728
> URL: https://issues.apache.org/jira/browse/NIFI-2728
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: 1.0.0
> Reporter: Andre
>
> travis-ci is currently broken and frequently reporting
> {{GC overhead limit exceeded}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
