[
https://issues.apache.org/jira/browse/BEAM-4706?focusedWorklogId=118737&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-118737
]
ASF GitHub Bot logged work on BEAM-4706:
----------------------------------------
Author: ASF GitHub Bot
Created on: 03/Jul/18 14:47
Start Date: 03/Jul/18 14:47
Worklog Time Spent: 10m
Work Description: kkucharc commented on a change in pull request #5877:
[BEAM-4706] BigQueryTornadoesIT cannot be run using integrationTest and
performanceTest tasks
URL: https://github.com/apache/beam/pull/5877#discussion_r199835060
##########
File path:
examples/java/src/test/java/org/apache/beam/examples/cookbook/BigQueryTornadoesIT.java
##########
@@ -28,7 +28,23 @@
import org.junit.runner.RunWith;
import org.junit.runners.JUnit4;
-/** End-to-end tests of BigQueryTornadoes. */
+/**
+ * An end-to-end tests of {@link
org.apache.beam.examples.cookbook.BigQueryTornadoes}.
+ *
+ * <p>This test uses the data from an external source defined in {@link
Review comment:
Ok, I checked it and changed.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 118737)
Time Spent: 1.5h (was: 1h 20m)
> BigQueryTornadoesIT cannot be run using integrationTest and performanceTest
> tasks
> ---------------------------------------------------------------------------------
>
> Key: BEAM-4706
> URL: https://issues.apache.org/jira/browse/BEAM-4706
> Project: Beam
> Issue Type: Bug
> Components: testing
> Reporter: Łukasz Gajowy
> Assignee: Kasia Kucharczyk
> Priority: Major
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> It seems that we cannot run this test using tasks from BuildModulePlugin
> designed to run such tests. Those are not included in build.gradle of
> examples module. There's a possibility that some other tests are not able to
> run due to this reason (this also has to be checked).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
