Łukasz Gajowy created BEAM-3379:
-----------------------------------
Summary: PAssert not successful when running IOITs with Flink
runner
Key: BEAM-3379
URL: https://issues.apache.org/jira/browse/BEAM-3379
Project: Beam
Issue Type: Bug
Components: runner-flink
Reporter: Łukasz Gajowy
Assignee: Aljoscha Krettek
When running IOIT tests on Flink either with command:
{{mvn clean verify \-pl sdks/java/io/file-based-io-tests/ \-Pio-it
\-DintegrationTestPipelineOptions='\["\-\-runner=FlinkRunner",
"\-\-flinkMaster=localhost:6123", "\-\-numberOfRecords=100000",
"\-\-filenamePrefix=TEST",
"\-\-filesToStage=/Users/lukasz/Projects/apache-beam/beam/sdks/java/io/file-based-io-tests/target/beam-sdks-java-io-file-based-io-tests-2.3.0-SNAPSHOT-shaded.jar,/Users/lukasz/Projects/apache-beam/beam/sdks/java/io/file-based-io-tests/target/beam-sdks-java-io-file-based-io-tests-2.3.0-SNAPSHOT-tests.jar"\]'
-Dit.test=TextIOIT -Pflink-runner}}
or without the filesToStage argument but using modifications described in
BEAM-3371, we get the following error, even though the assertion is succesful
(checked manually):
java.lang.AssertionError:
Expected 1 successful assertions, but found 0.
Expected: is <1L>
but: was <0L>
at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:20)
at
org.apache.beam.sdk.testing.TestPipeline.verifyPAssertsSucceeded(TestPipeline.java:541)
at org.apache.beam.sdk.testing.TestPipeline.run(TestPipeline.java:359)
at org.apache.beam.sdk.testing.TestPipeline.run(TestPipeline.java:340)
at
org.apache.beam.sdk.io.text.TextIOIT.writeThenReadAll(TextIOIT.java:109)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at
org.apache.beam.sdk.testing.TestPipeline$1.evaluate(TestPipeline.java:329)
at org.junit.rules.RunRules.evaluate(RunRules.java:20)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at
org.apache.maven.surefire.junitcore.pc.Scheduler$1.run(Scheduler.java:393)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
