[
https://issues.apache.org/jira/browse/KAFKA-6889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16508285#comment-16508285
]
Stanislav Kozlovski commented on KAFKA-6889:
--------------------------------------------
What do you mean the Jenkins has read access?
I personally cannot open the link sent by Matthias - https://imgur.com/yt7Su2e
> Fix Streams system test to only specify used log files
> ------------------------------------------------------
>
> Key: KAFKA-6889
> URL: https://issues.apache.org/jira/browse/KAFKA-6889
> Project: Kafka
> Issue Type: Task
> Components: streams, system tests
> Reporter: Matthias J. Sax
> Priority: Minor
> Labels: beginner, easyfix
>
> In `streams.py` the class `StreamsTestBaseService` lists many log files that
> are only used in certain tests. For all tests, that do not use those log
> files, during the test run WARN messages are produced:
> {noformat}
> [WARNING - 2018-05-09 13:51:22,065 - test - compress_service_logs -
> lineno:131]: Error compressing log /mnt/streams/streams.stdout.0-6: service
> <StreamsSmokeTestJobRunnerService-0-140502617565072: num_nodes: 1, nodes:
> ['worker7']>: ubuntu@worker7: Command 'cd "$(dirname
> /mnt/streams/streams.stdout.0-6)" && f="$(basename
> /mnt/streams/streams.stdout.0-6)" && tar czf "$f.tgz" "$f" && rm -rf
> /mnt/streams/streams.stdout.0-6' returned non-zero exit status 2. Remote
> error message: tar: streams.stdout.0-6: Cannot stat: No such file or directory
> tar: Exiting with failure status due to previous errors
> {noformat}
> Those message spam the output and might be miss leading. We should update the
> Streams system tests accordingly such that each test only specifies the
> log-file names it actually uses to avoid the WARN message.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
