You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@storm.apache.org by "Jungtaek Lim (JIRA)" <ji...@apache.org> on 2015/06/11 15:03:00 UTC
[jira] [Updated] (STORM-864) Exclude storm-kafka tests from Travis
CI build
[ https://issues.apache.org/jira/browse/STORM-864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jungtaek Lim updated STORM-864:
-------------------------------
Description:
We observed almost test fails from Travis CI are due to storm-kafka.
It is really bad, and I adjust backoff timeout values to bigger with no luck. It makes another strange issues, which makes me blocked.
IMO it seems to be an issue with slow machine, so for now we can just turn off storm-kafka tests from Travis CI build and make it stable first.
We can try to resolve origin issue later, though I'm wondering it could be solved without excluding tests.
was:
We observed almost test fails from Travis CI are due to storm-kafka.
It is really bad, and I adjust timeout values to bigger with no luck.
It makes another strange issues, which makes me blocked.
IMO it seems to be an issue with slow machine, so for now we can just turn off storm-kafka tests from Travis CI build and make it stable first.
We can try to resolve origin issue later, though I'm wondering it could be solved without excluding tests.
> Exclude storm-kafka tests from Travis CI build
> ----------------------------------------------
>
> Key: STORM-864
> URL: https://issues.apache.org/jira/browse/STORM-864
> Project: Apache Storm
> Issue Type: Sub-task
> Components: storm-kafka
> Reporter: Jungtaek Lim
> Priority: Minor
>
> We observed almost test fails from Travis CI are due to storm-kafka.
> It is really bad, and I adjust backoff timeout values to bigger with no luck. It makes another strange issues, which makes me blocked.
> IMO it seems to be an issue with slow machine, so for now we can just turn off storm-kafka tests from Travis CI build and make it stable first.
> We can try to resolve origin issue later, though I'm wondering it could be solved without excluding tests.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)