[
https://issues.apache.org/jira/browse/APEXMALHAR-2465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15952302#comment-15952302
]
Thomas Weise commented on APEXMALHAR-2465:
------------------------------------------
It is important that the CI infrastructure functions properly. Before the extra
examples were added, there were already too many build failures, but now the
Travis build is fully defunct. I would request that this is being looked into
before further examples are added.
Travis has a limit on the amount of logs, and the build (when run in Travis)
was setup to reduce the logging. Look for property test.log.console.threshold -
it isn't used in the newly added examples. After this is fixed, we can further
limit what gets logged if necessary, the CI is not there for elaborate logging
but to execute automated checks that tell us whether the build is good or not.
I would also suggest to centralize the log4j properties in Malhar instead of
repeating it for every project. This can probably be done as shared resource in
test scope. I will file a JIRA for it.
For other examples, before they get merged, please document on the respective
JIRA:
* example has automated test that covers it sufficiently
* example does not fill console with irrelevant logging
* example is built as part of CI (unlike parser project) and passes CI build
> Travis build is failing because of excessive logging
> ----------------------------------------------------
>
> Key: APEXMALHAR-2465
> URL: https://issues.apache.org/jira/browse/APEXMALHAR-2465
> Project: Apache Apex Malhar
> Issue Type: Bug
> Reporter: Velineni Lakshmi Prasanna
> Priority: Minor
>
> Recently many examples were added from datatorrent/examples. This seems to
> have pushed the amount of logs been generated during running of tests in the
> build, beyond the limit of what Travis allows. This is causing Travis build
> to fail. This needs to be addressed.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
