You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@apex.apache.org by Munagala Ramanath <ra...@datatorrent.com> on 2016/05/14 17:19:18 UTC
Why @Ignore on Kafka tests ?
Why is KafkaInputOperatorTest annotated with @Ignore ? This makes the test
not runnable from the commandline with maven.
Ram
Re: Why @Ignore on Kafka tests ?
Posted by Munagala Ramanath <ra...@datatorrent.com>.
Thanks David, that works. I also needed to go to my profile page (e.g.
https://travis-ci.org/profile/<login>) and
enable the malhar repo for Travis builds.
Ram
On Mon, May 16, 2016 at 11:17 AM, David Yan <da...@datatorrent.com> wrote:
> You can sign up for a travis-ci account using your github, then remove all
> @Ignore from the Kafka unit tests and push to a branch in your own forked
> Malhar repository. Travis will automatically run the test for you and you
> can restart the test using the Travis web UI.
>
> David
>
> On Mon, May 16, 2016 at 11:13 AM, Munagala Ramanath <ra...@datatorrent.com>
> wrote:
>
> > How do I check that ?
> >
> > Ram
> >
> > On Mon, May 16, 2016 at 11:08 AM, Thomas Weise <th...@datatorrent.com>
> > wrote:
> >
> > > Ram,
> > >
> > > Which test fails in Travis, have you checked?
> > >
> > > Thanks
> > >
> > > On Mon, May 16, 2016 at 11:03 AM, Munagala Ramanath <
> ram@datatorrent.com
> > >
> > > wrote:
> > >
> > > > That seems like a good solution.
> > > >
> > > > I didn't find any way to run an ignored test but, an alternative,
> > though
> > > > not as good
> > > > as David's, is to add an exclusion stanza to the configuration of the
> > > > surefire plugin, e.g.
> > > > * <plugin>*
> > > > * <groupId>org.apache.maven.plugins</groupId>*
> > > > * <artifactId>maven-surefire-plugin</artifactId>*
> > > > * <configuration>*
> > > > * <excludes>*
> > > > * <exclude>**/ApplicationTest.java</exclude>*
> > > > * </excludes>*
> > > > * </configuration>*
> > > > * </plugin>*
> > > >
> > > > This suppresses the test for normal runs but can be explicitly
> > triggered
> > > > with:
> > > >
> > > > *mvn -Dtest=com.example.myapexapp.ApplicationTest test*
> > > >
> > > > Ram
> > > >
> > > > On Mon, May 16, 2016 at 10:50 AM, David Yan <da...@datatorrent.com>
> > > wrote:
> > > >
> > > > > If it only fails on Travis and *never* fails elsewhere, you can use
> > the
> > > > > function StramTestSupport.isInTravis() method.
> > > > > Here's an example snippet from StreamingContainerManagerTest.java:
> > > > >
> > > > > if (StramTestSupport.isInTravis()) {
> > > > > // disable this test in travis because of an intermittent
> > problem
> > > > > similar to this:
> > > > > //
> > > > >
> > > > >
> > > >
> > >
> >
> http://stackoverflow.com/questions/32172925/travis-ci-sporadic-timeouts-to-localhost
> > > > > // We should remove this when we find a solution to this.
> > > > > LOG.info("Test testAppDataPush is disabled in Travis");
> > > > > return;
> > > > > }
> > > > >
> > > > > David
> > > > >
> > > > > On Mon, May 16, 2016 at 9:59 AM, Siyuan Hua <
> siyuan@datatorrent.com>
> > > > > wrote:
> > > > >
> > > > > > Ram, Thomas
> > > > > > The last time I tried, the tests only fail in travis. Is there a
> > way
> > > > > ignore
> > > > > > the test in maven build by default and test it locally with some
> > > maven
> > > > > > command line options?
> > > > > >
> > > > > > Regards,
> > > > > > Siyuan
> > > > > >
> > > > > > On Sat, May 14, 2016 at 10:37 AM, Thomas Weise <
> > > thomas@datatorrent.com
> > > > >
> > > > > > wrote:
> > > > > >
> > > > > > > Ram,
> > > > > > >
> > > > > > > There were problems with some of the tests but also with
> running
> > > them
> > > > > in
> > > > > > > Travis CI overall (the latter has been fixed meanwhile.)
> > > > > > >
> > > > > > > Can you please try to enable the tests and see if they pass in
> > > > Travis,
> > > > > we
> > > > > > > should then only mark @Ignore those that actually still need to
> > be
> > > > > fixed.
> > > > > > >
> > > > > > > Thanks
> > > > > > >
> > > > > > > On Sat, May 14, 2016 at 10:19 AM, Munagala Ramanath <
> > > > > ram@datatorrent.com
> > > > > > >
> > > > > > > wrote:
> > > > > > >
> > > > > > > > Why is KafkaInputOperatorTest annotated with @Ignore ? This
> > makes
> > > > the
> > > > > > > test
> > > > > > > > not runnable from the commandline with maven.
> > > > > > > >
> > > > > > > > Ram
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
Re: Why @Ignore on Kafka tests ?
Posted by David Yan <da...@datatorrent.com>.
You can sign up for a travis-ci account using your github, then remove all
@Ignore from the Kafka unit tests and push to a branch in your own forked
Malhar repository. Travis will automatically run the test for you and you
can restart the test using the Travis web UI.
David
On Mon, May 16, 2016 at 11:13 AM, Munagala Ramanath <ra...@datatorrent.com>
wrote:
> How do I check that ?
>
> Ram
>
> On Mon, May 16, 2016 at 11:08 AM, Thomas Weise <th...@datatorrent.com>
> wrote:
>
> > Ram,
> >
> > Which test fails in Travis, have you checked?
> >
> > Thanks
> >
> > On Mon, May 16, 2016 at 11:03 AM, Munagala Ramanath <ram@datatorrent.com
> >
> > wrote:
> >
> > > That seems like a good solution.
> > >
> > > I didn't find any way to run an ignored test but, an alternative,
> though
> > > not as good
> > > as David's, is to add an exclusion stanza to the configuration of the
> > > surefire plugin, e.g.
> > > * <plugin>*
> > > * <groupId>org.apache.maven.plugins</groupId>*
> > > * <artifactId>maven-surefire-plugin</artifactId>*
> > > * <configuration>*
> > > * <excludes>*
> > > * <exclude>**/ApplicationTest.java</exclude>*
> > > * </excludes>*
> > > * </configuration>*
> > > * </plugin>*
> > >
> > > This suppresses the test for normal runs but can be explicitly
> triggered
> > > with:
> > >
> > > *mvn -Dtest=com.example.myapexapp.ApplicationTest test*
> > >
> > > Ram
> > >
> > > On Mon, May 16, 2016 at 10:50 AM, David Yan <da...@datatorrent.com>
> > wrote:
> > >
> > > > If it only fails on Travis and *never* fails elsewhere, you can use
> the
> > > > function StramTestSupport.isInTravis() method.
> > > > Here's an example snippet from StreamingContainerManagerTest.java:
> > > >
> > > > if (StramTestSupport.isInTravis()) {
> > > > // disable this test in travis because of an intermittent
> problem
> > > > similar to this:
> > > > //
> > > >
> > > >
> > >
> >
> http://stackoverflow.com/questions/32172925/travis-ci-sporadic-timeouts-to-localhost
> > > > // We should remove this when we find a solution to this.
> > > > LOG.info("Test testAppDataPush is disabled in Travis");
> > > > return;
> > > > }
> > > >
> > > > David
> > > >
> > > > On Mon, May 16, 2016 at 9:59 AM, Siyuan Hua <si...@datatorrent.com>
> > > > wrote:
> > > >
> > > > > Ram, Thomas
> > > > > The last time I tried, the tests only fail in travis. Is there a
> way
> > > > ignore
> > > > > the test in maven build by default and test it locally with some
> > maven
> > > > > command line options?
> > > > >
> > > > > Regards,
> > > > > Siyuan
> > > > >
> > > > > On Sat, May 14, 2016 at 10:37 AM, Thomas Weise <
> > thomas@datatorrent.com
> > > >
> > > > > wrote:
> > > > >
> > > > > > Ram,
> > > > > >
> > > > > > There were problems with some of the tests but also with running
> > them
> > > > in
> > > > > > Travis CI overall (the latter has been fixed meanwhile.)
> > > > > >
> > > > > > Can you please try to enable the tests and see if they pass in
> > > Travis,
> > > > we
> > > > > > should then only mark @Ignore those that actually still need to
> be
> > > > fixed.
> > > > > >
> > > > > > Thanks
> > > > > >
> > > > > > On Sat, May 14, 2016 at 10:19 AM, Munagala Ramanath <
> > > > ram@datatorrent.com
> > > > > >
> > > > > > wrote:
> > > > > >
> > > > > > > Why is KafkaInputOperatorTest annotated with @Ignore ? This
> makes
> > > the
> > > > > > test
> > > > > > > not runnable from the commandline with maven.
> > > > > > >
> > > > > > > Ram
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
Re: Why @Ignore on Kafka tests ?
Posted by Munagala Ramanath <ra...@datatorrent.com>.
How do I check that ?
Ram
On Mon, May 16, 2016 at 11:08 AM, Thomas Weise <th...@datatorrent.com>
wrote:
> Ram,
>
> Which test fails in Travis, have you checked?
>
> Thanks
>
> On Mon, May 16, 2016 at 11:03 AM, Munagala Ramanath <ra...@datatorrent.com>
> wrote:
>
> > That seems like a good solution.
> >
> > I didn't find any way to run an ignored test but, an alternative, though
> > not as good
> > as David's, is to add an exclusion stanza to the configuration of the
> > surefire plugin, e.g.
> > * <plugin>*
> > * <groupId>org.apache.maven.plugins</groupId>*
> > * <artifactId>maven-surefire-plugin</artifactId>*
> > * <configuration>*
> > * <excludes>*
> > * <exclude>**/ApplicationTest.java</exclude>*
> > * </excludes>*
> > * </configuration>*
> > * </plugin>*
> >
> > This suppresses the test for normal runs but can be explicitly triggered
> > with:
> >
> > *mvn -Dtest=com.example.myapexapp.ApplicationTest test*
> >
> > Ram
> >
> > On Mon, May 16, 2016 at 10:50 AM, David Yan <da...@datatorrent.com>
> wrote:
> >
> > > If it only fails on Travis and *never* fails elsewhere, you can use the
> > > function StramTestSupport.isInTravis() method.
> > > Here's an example snippet from StreamingContainerManagerTest.java:
> > >
> > > if (StramTestSupport.isInTravis()) {
> > > // disable this test in travis because of an intermittent problem
> > > similar to this:
> > > //
> > >
> > >
> >
> http://stackoverflow.com/questions/32172925/travis-ci-sporadic-timeouts-to-localhost
> > > // We should remove this when we find a solution to this.
> > > LOG.info("Test testAppDataPush is disabled in Travis");
> > > return;
> > > }
> > >
> > > David
> > >
> > > On Mon, May 16, 2016 at 9:59 AM, Siyuan Hua <si...@datatorrent.com>
> > > wrote:
> > >
> > > > Ram, Thomas
> > > > The last time I tried, the tests only fail in travis. Is there a way
> > > ignore
> > > > the test in maven build by default and test it locally with some
> maven
> > > > command line options?
> > > >
> > > > Regards,
> > > > Siyuan
> > > >
> > > > On Sat, May 14, 2016 at 10:37 AM, Thomas Weise <
> thomas@datatorrent.com
> > >
> > > > wrote:
> > > >
> > > > > Ram,
> > > > >
> > > > > There were problems with some of the tests but also with running
> them
> > > in
> > > > > Travis CI overall (the latter has been fixed meanwhile.)
> > > > >
> > > > > Can you please try to enable the tests and see if they pass in
> > Travis,
> > > we
> > > > > should then only mark @Ignore those that actually still need to be
> > > fixed.
> > > > >
> > > > > Thanks
> > > > >
> > > > > On Sat, May 14, 2016 at 10:19 AM, Munagala Ramanath <
> > > ram@datatorrent.com
> > > > >
> > > > > wrote:
> > > > >
> > > > > > Why is KafkaInputOperatorTest annotated with @Ignore ? This makes
> > the
> > > > > test
> > > > > > not runnable from the commandline with maven.
> > > > > >
> > > > > > Ram
> > > > > >
> > > > >
> > > >
> > >
> >
>
Re: Why @Ignore on Kafka tests ?
Posted by Chandni Singh <si...@gmail.com>.
There's a ticket for Managed state test failure and I am working on it.
On May 16, 2016 12:16 PM, "Munagala Ramanath" <ra...@datatorrent.com> wrote:
I got a failure but well before it reached kafka:
testFreeWindowTransferRaceCondition(org.apache.apex.malhar.lib.state.managed.ManagedStateImplTest)
Time elapsed: 3.074 sec <<< ERROR!
java.lang.NullPointerException: null
at
com.datatorrent.lib.util.comparator.SliceComparator.compare(SliceComparator.java:37)
at
com.datatorrent.lib.util.comparator.SliceComparator.compare(SliceComparator.java:32)
at
org.apache.apex.malhar.lib.state.managed.Bucket$DefaultBucket.getFromReaders(Bucket.java:289)
at
org.apache.apex.malhar.lib.state.managed.Bucket$DefaultBucket.get(Bucket.java:324)
at
org.apache.apex.malhar.lib.state.managed.AbstractManagedStateImpl.getValueFromBucketSync(AbstractManagedStateImpl.java:288)
at
org.apache.apex.malhar.lib.state.managed.ManagedStateImpl.getSync(ManagedStateImpl.java:63)
at
org.apache.apex.malhar.lib.state.managed.ManagedStateImplTest.testFreeWindowTransferRaceCondition(ManagedStateImplTest.java:200)
All tests thereafter were skipped.
Ram
On Mon, May 16, 2016 at 11:08 AM, Thomas Weise <th...@datatorrent.com>
wrote:
> Ram,
>
> Which test fails in Travis, have you checked?
>
> Thanks
>
> On Mon, May 16, 2016 at 11:03 AM, Munagala Ramanath <ra...@datatorrent.com>
> wrote:
>
> > That seems like a good solution.
> >
> > I didn't find any way to run an ignored test but, an alternative, though
> > not as good
> > as David's, is to add an exclusion stanza to the configuration of the
> > surefire plugin, e.g.
> > * <plugin>*
> > * <groupId>org.apache.maven.plugins</groupId>*
> > * <artifactId>maven-surefire-plugin</artifactId>*
> > * <configuration>*
> > * <excludes>*
> > * <exclude>**/ApplicationTest.java</exclude>*
> > * </excludes>*
> > * </configuration>*
> > * </plugin>*
> >
> > This suppresses the test for normal runs but can be explicitly triggered
> > with:
> >
> > *mvn -Dtest=com.example.myapexapp.ApplicationTest test*
> >
> > Ram
> >
> > On Mon, May 16, 2016 at 10:50 AM, David Yan <da...@datatorrent.com>
> wrote:
> >
> > > If it only fails on Travis and *never* fails elsewhere, you can use
the
> > > function StramTestSupport.isInTravis() method.
> > > Here's an example snippet from StreamingContainerManagerTest.java:
> > >
> > > if (StramTestSupport.isInTravis()) {
> > > // disable this test in travis because of an intermittent
problem
> > > similar to this:
> > > //
> > >
> > >
> >
>
http://stackoverflow.com/questions/32172925/travis-ci-sporadic-timeouts-to-localhost
> > > // We should remove this when we find a solution to this.
> > > LOG.info("Test testAppDataPush is disabled in Travis");
> > > return;
> > > }
> > >
> > > David
> > >
> > > On Mon, May 16, 2016 at 9:59 AM, Siyuan Hua <si...@datatorrent.com>
> > > wrote:
> > >
> > > > Ram, Thomas
> > > > The last time I tried, the tests only fail in travis. Is there a way
> > > ignore
> > > > the test in maven build by default and test it locally with some
> maven
> > > > command line options?
> > > >
> > > > Regards,
> > > > Siyuan
> > > >
> > > > On Sat, May 14, 2016 at 10:37 AM, Thomas Weise <
> thomas@datatorrent.com
> > >
> > > > wrote:
> > > >
> > > > > Ram,
> > > > >
> > > > > There were problems with some of the tests but also with running
> them
> > > in
> > > > > Travis CI overall (the latter has been fixed meanwhile.)
> > > > >
> > > > > Can you please try to enable the tests and see if they pass in
> > Travis,
> > > we
> > > > > should then only mark @Ignore those that actually still need to be
> > > fixed.
> > > > >
> > > > > Thanks
> > > > >
> > > > > On Sat, May 14, 2016 at 10:19 AM, Munagala Ramanath <
> > > ram@datatorrent.com
> > > > >
> > > > > wrote:
> > > > >
> > > > > > Why is KafkaInputOperatorTest annotated with @Ignore ? This
makes
> > the
> > > > > test
> > > > > > not runnable from the commandline with maven.
> > > > > >
> > > > > > Ram
> > > > > >
> > > > >
> > > >
> > >
> >
>
Re: Why @Ignore on Kafka tests ?
Posted by Munagala Ramanath <ra...@datatorrent.com>.
I got a failure but well before it reached kafka:
testFreeWindowTransferRaceCondition(org.apache.apex.malhar.lib.state.managed.ManagedStateImplTest)
Time elapsed: 3.074 sec <<< ERROR!
java.lang.NullPointerException: null
at
com.datatorrent.lib.util.comparator.SliceComparator.compare(SliceComparator.java:37)
at
com.datatorrent.lib.util.comparator.SliceComparator.compare(SliceComparator.java:32)
at
org.apache.apex.malhar.lib.state.managed.Bucket$DefaultBucket.getFromReaders(Bucket.java:289)
at
org.apache.apex.malhar.lib.state.managed.Bucket$DefaultBucket.get(Bucket.java:324)
at
org.apache.apex.malhar.lib.state.managed.AbstractManagedStateImpl.getValueFromBucketSync(AbstractManagedStateImpl.java:288)
at
org.apache.apex.malhar.lib.state.managed.ManagedStateImpl.getSync(ManagedStateImpl.java:63)
at
org.apache.apex.malhar.lib.state.managed.ManagedStateImplTest.testFreeWindowTransferRaceCondition(ManagedStateImplTest.java:200)
All tests thereafter were skipped.
Ram
On Mon, May 16, 2016 at 11:08 AM, Thomas Weise <th...@datatorrent.com>
wrote:
> Ram,
>
> Which test fails in Travis, have you checked?
>
> Thanks
>
> On Mon, May 16, 2016 at 11:03 AM, Munagala Ramanath <ra...@datatorrent.com>
> wrote:
>
> > That seems like a good solution.
> >
> > I didn't find any way to run an ignored test but, an alternative, though
> > not as good
> > as David's, is to add an exclusion stanza to the configuration of the
> > surefire plugin, e.g.
> > * <plugin>*
> > * <groupId>org.apache.maven.plugins</groupId>*
> > * <artifactId>maven-surefire-plugin</artifactId>*
> > * <configuration>*
> > * <excludes>*
> > * <exclude>**/ApplicationTest.java</exclude>*
> > * </excludes>*
> > * </configuration>*
> > * </plugin>*
> >
> > This suppresses the test for normal runs but can be explicitly triggered
> > with:
> >
> > *mvn -Dtest=com.example.myapexapp.ApplicationTest test*
> >
> > Ram
> >
> > On Mon, May 16, 2016 at 10:50 AM, David Yan <da...@datatorrent.com>
> wrote:
> >
> > > If it only fails on Travis and *never* fails elsewhere, you can use the
> > > function StramTestSupport.isInTravis() method.
> > > Here's an example snippet from StreamingContainerManagerTest.java:
> > >
> > > if (StramTestSupport.isInTravis()) {
> > > // disable this test in travis because of an intermittent problem
> > > similar to this:
> > > //
> > >
> > >
> >
> http://stackoverflow.com/questions/32172925/travis-ci-sporadic-timeouts-to-localhost
> > > // We should remove this when we find a solution to this.
> > > LOG.info("Test testAppDataPush is disabled in Travis");
> > > return;
> > > }
> > >
> > > David
> > >
> > > On Mon, May 16, 2016 at 9:59 AM, Siyuan Hua <si...@datatorrent.com>
> > > wrote:
> > >
> > > > Ram, Thomas
> > > > The last time I tried, the tests only fail in travis. Is there a way
> > > ignore
> > > > the test in maven build by default and test it locally with some
> maven
> > > > command line options?
> > > >
> > > > Regards,
> > > > Siyuan
> > > >
> > > > On Sat, May 14, 2016 at 10:37 AM, Thomas Weise <
> thomas@datatorrent.com
> > >
> > > > wrote:
> > > >
> > > > > Ram,
> > > > >
> > > > > There were problems with some of the tests but also with running
> them
> > > in
> > > > > Travis CI overall (the latter has been fixed meanwhile.)
> > > > >
> > > > > Can you please try to enable the tests and see if they pass in
> > Travis,
> > > we
> > > > > should then only mark @Ignore those that actually still need to be
> > > fixed.
> > > > >
> > > > > Thanks
> > > > >
> > > > > On Sat, May 14, 2016 at 10:19 AM, Munagala Ramanath <
> > > ram@datatorrent.com
> > > > >
> > > > > wrote:
> > > > >
> > > > > > Why is KafkaInputOperatorTest annotated with @Ignore ? This makes
> > the
> > > > > test
> > > > > > not runnable from the commandline with maven.
> > > > > >
> > > > > > Ram
> > > > > >
> > > > >
> > > >
> > >
> >
>
Re: Why @Ignore on Kafka tests ?
Posted by Thomas Weise <th...@datatorrent.com>.
Ram,
Which test fails in Travis, have you checked?
Thanks
On Mon, May 16, 2016 at 11:03 AM, Munagala Ramanath <ra...@datatorrent.com>
wrote:
> That seems like a good solution.
>
> I didn't find any way to run an ignored test but, an alternative, though
> not as good
> as David's, is to add an exclusion stanza to the configuration of the
> surefire plugin, e.g.
> * <plugin>*
> * <groupId>org.apache.maven.plugins</groupId>*
> * <artifactId>maven-surefire-plugin</artifactId>*
> * <configuration>*
> * <excludes>*
> * <exclude>**/ApplicationTest.java</exclude>*
> * </excludes>*
> * </configuration>*
> * </plugin>*
>
> This suppresses the test for normal runs but can be explicitly triggered
> with:
>
> *mvn -Dtest=com.example.myapexapp.ApplicationTest test*
>
> Ram
>
> On Mon, May 16, 2016 at 10:50 AM, David Yan <da...@datatorrent.com> wrote:
>
> > If it only fails on Travis and *never* fails elsewhere, you can use the
> > function StramTestSupport.isInTravis() method.
> > Here's an example snippet from StreamingContainerManagerTest.java:
> >
> > if (StramTestSupport.isInTravis()) {
> > // disable this test in travis because of an intermittent problem
> > similar to this:
> > //
> >
> >
> http://stackoverflow.com/questions/32172925/travis-ci-sporadic-timeouts-to-localhost
> > // We should remove this when we find a solution to this.
> > LOG.info("Test testAppDataPush is disabled in Travis");
> > return;
> > }
> >
> > David
> >
> > On Mon, May 16, 2016 at 9:59 AM, Siyuan Hua <si...@datatorrent.com>
> > wrote:
> >
> > > Ram, Thomas
> > > The last time I tried, the tests only fail in travis. Is there a way
> > ignore
> > > the test in maven build by default and test it locally with some maven
> > > command line options?
> > >
> > > Regards,
> > > Siyuan
> > >
> > > On Sat, May 14, 2016 at 10:37 AM, Thomas Weise <thomas@datatorrent.com
> >
> > > wrote:
> > >
> > > > Ram,
> > > >
> > > > There were problems with some of the tests but also with running them
> > in
> > > > Travis CI overall (the latter has been fixed meanwhile.)
> > > >
> > > > Can you please try to enable the tests and see if they pass in
> Travis,
> > we
> > > > should then only mark @Ignore those that actually still need to be
> > fixed.
> > > >
> > > > Thanks
> > > >
> > > > On Sat, May 14, 2016 at 10:19 AM, Munagala Ramanath <
> > ram@datatorrent.com
> > > >
> > > > wrote:
> > > >
> > > > > Why is KafkaInputOperatorTest annotated with @Ignore ? This makes
> the
> > > > test
> > > > > not runnable from the commandline with maven.
> > > > >
> > > > > Ram
> > > > >
> > > >
> > >
> >
>
Re: Why @Ignore on Kafka tests ?
Posted by Munagala Ramanath <ra...@datatorrent.com>.
That seems like a good solution.
I didn't find any way to run an ignored test but, an alternative, though
not as good
as David's, is to add an exclusion stanza to the configuration of the
surefire plugin, e.g.
* <plugin>*
* <groupId>org.apache.maven.plugins</groupId>*
* <artifactId>maven-surefire-plugin</artifactId>*
* <configuration>*
* <excludes>*
* <exclude>**/ApplicationTest.java</exclude>*
* </excludes>*
* </configuration>*
* </plugin>*
This suppresses the test for normal runs but can be explicitly triggered
with:
*mvn -Dtest=com.example.myapexapp.ApplicationTest test*
Ram
On Mon, May 16, 2016 at 10:50 AM, David Yan <da...@datatorrent.com> wrote:
> If it only fails on Travis and *never* fails elsewhere, you can use the
> function StramTestSupport.isInTravis() method.
> Here's an example snippet from StreamingContainerManagerTest.java:
>
> if (StramTestSupport.isInTravis()) {
> // disable this test in travis because of an intermittent problem
> similar to this:
> //
>
> http://stackoverflow.com/questions/32172925/travis-ci-sporadic-timeouts-to-localhost
> // We should remove this when we find a solution to this.
> LOG.info("Test testAppDataPush is disabled in Travis");
> return;
> }
>
> David
>
> On Mon, May 16, 2016 at 9:59 AM, Siyuan Hua <si...@datatorrent.com>
> wrote:
>
> > Ram, Thomas
> > The last time I tried, the tests only fail in travis. Is there a way
> ignore
> > the test in maven build by default and test it locally with some maven
> > command line options?
> >
> > Regards,
> > Siyuan
> >
> > On Sat, May 14, 2016 at 10:37 AM, Thomas Weise <th...@datatorrent.com>
> > wrote:
> >
> > > Ram,
> > >
> > > There were problems with some of the tests but also with running them
> in
> > > Travis CI overall (the latter has been fixed meanwhile.)
> > >
> > > Can you please try to enable the tests and see if they pass in Travis,
> we
> > > should then only mark @Ignore those that actually still need to be
> fixed.
> > >
> > > Thanks
> > >
> > > On Sat, May 14, 2016 at 10:19 AM, Munagala Ramanath <
> ram@datatorrent.com
> > >
> > > wrote:
> > >
> > > > Why is KafkaInputOperatorTest annotated with @Ignore ? This makes the
> > > test
> > > > not runnable from the commandline with maven.
> > > >
> > > > Ram
> > > >
> > >
> >
>
Re: Why @Ignore on Kafka tests ?
Posted by David Yan <da...@datatorrent.com>.
If it only fails on Travis and *never* fails elsewhere, you can use the
function StramTestSupport.isInTravis() method.
Here's an example snippet from StreamingContainerManagerTest.java:
if (StramTestSupport.isInTravis()) {
// disable this test in travis because of an intermittent problem
similar to this:
//
http://stackoverflow.com/questions/32172925/travis-ci-sporadic-timeouts-to-localhost
// We should remove this when we find a solution to this.
LOG.info("Test testAppDataPush is disabled in Travis");
return;
}
David
On Mon, May 16, 2016 at 9:59 AM, Siyuan Hua <si...@datatorrent.com> wrote:
> Ram, Thomas
> The last time I tried, the tests only fail in travis. Is there a way ignore
> the test in maven build by default and test it locally with some maven
> command line options?
>
> Regards,
> Siyuan
>
> On Sat, May 14, 2016 at 10:37 AM, Thomas Weise <th...@datatorrent.com>
> wrote:
>
> > Ram,
> >
> > There were problems with some of the tests but also with running them in
> > Travis CI overall (the latter has been fixed meanwhile.)
> >
> > Can you please try to enable the tests and see if they pass in Travis, we
> > should then only mark @Ignore those that actually still need to be fixed.
> >
> > Thanks
> >
> > On Sat, May 14, 2016 at 10:19 AM, Munagala Ramanath <ram@datatorrent.com
> >
> > wrote:
> >
> > > Why is KafkaInputOperatorTest annotated with @Ignore ? This makes the
> > test
> > > not runnable from the commandline with maven.
> > >
> > > Ram
> > >
> >
>
Re: Why @Ignore on Kafka tests ?
Posted by Thomas Weise <th...@datatorrent.com>.
Yes, that is possible but first we need to see exactly which tests really
have a problem.
On Mon, May 16, 2016 at 9:59 AM, Siyuan Hua <si...@datatorrent.com> wrote:
> Ram, Thomas
> The last time I tried, the tests only fail in travis. Is there a way ignore
> the test in maven build by default and test it locally with some maven
> command line options?
>
> Regards,
> Siyuan
>
> On Sat, May 14, 2016 at 10:37 AM, Thomas Weise <th...@datatorrent.com>
> wrote:
>
> > Ram,
> >
> > There were problems with some of the tests but also with running them in
> > Travis CI overall (the latter has been fixed meanwhile.)
> >
> > Can you please try to enable the tests and see if they pass in Travis, we
> > should then only mark @Ignore those that actually still need to be fixed.
> >
> > Thanks
> >
> > On Sat, May 14, 2016 at 10:19 AM, Munagala Ramanath <ram@datatorrent.com
> >
> > wrote:
> >
> > > Why is KafkaInputOperatorTest annotated with @Ignore ? This makes the
> > test
> > > not runnable from the commandline with maven.
> > >
> > > Ram
> > >
> >
>
Re: Why @Ignore on Kafka tests ?
Posted by Siyuan Hua <si...@datatorrent.com>.
Ram, Thomas
The last time I tried, the tests only fail in travis. Is there a way ignore
the test in maven build by default and test it locally with some maven
command line options?
Regards,
Siyuan
On Sat, May 14, 2016 at 10:37 AM, Thomas Weise <th...@datatorrent.com>
wrote:
> Ram,
>
> There were problems with some of the tests but also with running them in
> Travis CI overall (the latter has been fixed meanwhile.)
>
> Can you please try to enable the tests and see if they pass in Travis, we
> should then only mark @Ignore those that actually still need to be fixed.
>
> Thanks
>
> On Sat, May 14, 2016 at 10:19 AM, Munagala Ramanath <ra...@datatorrent.com>
> wrote:
>
> > Why is KafkaInputOperatorTest annotated with @Ignore ? This makes the
> test
> > not runnable from the commandline with maven.
> >
> > Ram
> >
>
Re: Why @Ignore on Kafka tests ?
Posted by Thomas Weise <th...@datatorrent.com>.
Ram,
There were problems with some of the tests but also with running them in
Travis CI overall (the latter has been fixed meanwhile.)
Can you please try to enable the tests and see if they pass in Travis, we
should then only mark @Ignore those that actually still need to be fixed.
Thanks
On Sat, May 14, 2016 at 10:19 AM, Munagala Ramanath <ra...@datatorrent.com>
wrote:
> Why is KafkaInputOperatorTest annotated with @Ignore ? This makes the test
> not runnable from the commandline with maven.
>
> Ram
>