Skip to content

Conversation

@echauchot
Copy link
Contributor

R: @aromanenko-dev


Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

  • Choose reviewer(s) and mention them in a comment (R: @username).
  • Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
  • If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

Post-Commit Tests Status (on master branch)

Lang SDK Apex Dataflow Flink Gearpump Samza Spark
Go Build Status --- --- Build Status --- --- Build Status
Java Build Status Build Status Build Status Build Status
Build Status
Build Status
Build Status Build Status Build Status
Build Status
Build Status
Python Build Status
Build Status
Build Status
Build Status
--- Build Status
Build Status
Build Status
Build Status
--- --- Build Status
XLang --- --- --- Build Status --- --- ---

Pre-Commit Tests Status (on master branch)

--- Java Python Go Website
Non-portable Build Status Build Status
Build Status
Build Status Build Status
Portable --- Build Status --- ---

See .test-infra/jenkins/README for trigger phrase, status and link of all Jenkins jobs.

Copy link
Contributor

@aromanenko-dev aromanenko-dev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, LGTM, just a minor question (see inline).
Also, please squash all commits before merging.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we really need to have DEBUG log level in tests by default?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

in test I think so because it prints Beam DAG and spark DAG

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm afraid to have too much logs for all Spark tests that could consume too much disk space on Jenkins servers (since Spark is very verbose).

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

well it is just for the runner not for the spark engine. And the runner puts so few logs (I think only the DAGs).
But anyway, it appears that for some reason, to have the debug logs even in UTests, it requires to change the production conf log file! Spark has always been quite difficult to set up with log4j. Maybe it is due to the test file named log4j-test.properties. Anyway I'll put it back to error until we figure out how to configure it properly.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The same question as above

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same answer than above :)

@echauchot
Copy link
Contributor Author

echauchot commented Dec 5, 2019

@aromanenko-dev thanks for the prompt review !
I'll squash the commits into the last one but commit 1 has nothing to do with the rest so I'll keep it separate.

@echauchot echauchot force-pushed the BEAM-8830-flattens-spark branch from 33ae949 to 41f3aa6 Compare December 5, 2019 14:13
@echauchot
Copy link
Contributor Author

done

@aromanenko-dev
Copy link
Contributor

Run Spark StructuredStreaming ValidatesRunner

@aromanenko-dev
Copy link
Contributor

Some ValidatesRunner tests started to fail even if they passed before

16:24:54 > Task :runners:spark:validatesStructuredStreamingRunnerBatch
16:39:08 
16:39:08 org.apache.beam.sdk.transforms.SplittableDoFnTest > testPairWithIndexWindowedTimestampedBounded FAILED
16:39:08     java.lang.RuntimeException at SplittableDoFnTest.java:220
16:39:08         Caused by: org.apache.spark.SparkException
16:39:08 
16:39:08 org.apache.beam.sdk.transforms.SplittableDoFnTest > testPairWithIndexBasicBounded FAILED
16:39:08     java.lang.IllegalStateException at SplittableDoFnTest.java:153
16:39:08 
16:39:08 org.apache.beam.sdk.transforms.SplittableDoFnTest > testOutputAfterCheckpointBounded FAILED
16:39:08     java.lang.IllegalStateException at SplittableDoFnTest.java:311
16:39:08 
16:39:08 org.apache.beam.sdk.transforms.SplittableDoFnTest > testAdditionalOutputBounded FAILED
16:39:08     java.lang.IllegalStateException at SplittableDoFnTest.java:637
16:39:36 
16:39:36 179 tests completed, 4 failed, 1 skipped

…at sets the schema to binary.

Remove test exclusions for now passing tests
Set test log level to debug
@echauchot echauchot force-pushed the BEAM-8830-flattens-spark branch from 41f3aa6 to 62bd3ff Compare December 5, 2019 15:56
@echauchot
Copy link
Contributor Author

Some ValidatesRunner tests started to fail even if they passed before

16:24:54 > Task :runners:spark:validatesStructuredStreamingRunnerBatch
16:39:08 
16:39:08 org.apache.beam.sdk.transforms.SplittableDoFnTest > testPairWithIndexWindowedTimestampedBounded FAILED
16:39:08     java.lang.RuntimeException at SplittableDoFnTest.java:220
16:39:08         Caused by: org.apache.spark.SparkException
16:39:08 
16:39:08 org.apache.beam.sdk.transforms.SplittableDoFnTest > testPairWithIndexBasicBounded FAILED
16:39:08     java.lang.IllegalStateException at SplittableDoFnTest.java:153
16:39:08 
16:39:08 org.apache.beam.sdk.transforms.SplittableDoFnTest > testOutputAfterCheckpointBounded FAILED
16:39:08     java.lang.IllegalStateException at SplittableDoFnTest.java:311
16:39:08 
16:39:08 org.apache.beam.sdk.transforms.SplittableDoFnTest > testAdditionalOutputBounded FAILED
16:39:08     java.lang.IllegalStateException at SplittableDoFnTest.java:637
16:39:36 
16:39:36 179 tests completed, 4 failed, 1 skipped

Strange because it does not use emptyDataset (the only thing that has changed). It might be a side effect, I'll take a look

@echauchot
Copy link
Contributor Author

Some ValidatesRunner tests started to fail even if they passed before

16:24:54 > Task :runners:spark:validatesStructuredStreamingRunnerBatch
16:39:08 
16:39:08 org.apache.beam.sdk.transforms.SplittableDoFnTest > testPairWithIndexWindowedTimestampedBounded FAILED
16:39:08     java.lang.RuntimeException at SplittableDoFnTest.java:220
16:39:08         Caused by: org.apache.spark.SparkException
16:39:08 
16:39:08 org.apache.beam.sdk.transforms.SplittableDoFnTest > testPairWithIndexBasicBounded FAILED
16:39:08     java.lang.IllegalStateException at SplittableDoFnTest.java:153
16:39:08 
16:39:08 org.apache.beam.sdk.transforms.SplittableDoFnTest > testOutputAfterCheckpointBounded FAILED
16:39:08     java.lang.IllegalStateException at SplittableDoFnTest.java:311
16:39:08 
16:39:08 org.apache.beam.sdk.transforms.SplittableDoFnTest > testAdditionalOutputBounded FAILED
16:39:08     java.lang.IllegalStateException at SplittableDoFnTest.java:637
16:39:36 
16:39:36 179 tests completed, 4 failed, 1 skipped

Strange because it does not use emptyDataset (the only thing that has changed). It might be a side effect, I'll take a look

The test passes on my machine. Maybe an unrelated flaky test

@echauchot
Copy link
Contributor Author

Run Spark StructuredStreaming ValidatesRunner

@echauchot
Copy link
Contributor Author

@aromanenko-dev : OOM on last run of VR tests. one splittableDoFn test is taking 5 min I guess it is not normal. But anyway, SDF is not implemented on the runner. I think we should exclude all SDF tests. WDYT ?

@echauchot echauchot force-pushed the BEAM-8830-flattens-spark branch 2 times, most recently from 7b6f604 to 7dd8354 Compare December 9, 2019 09:30
@echauchot
Copy link
Contributor Author

echauchot commented Dec 9, 2019

@aromanenko-dev with @iemejia last comment I just reduced the SDF tests exclusion scope to only unbounded tests and testPairWithIndexWindowedTimestampedBounded that took 5 min in last run and that might be the case of the last OOM. Can we merge on green light ?

@echauchot echauchot force-pushed the BEAM-8830-flattens-spark branch from 7dd8354 to f67bc41 Compare December 9, 2019 09:36
@aromanenko-dev
Copy link
Contributor

Run Spark StructuredStreaming ValidatesRunner

@aromanenko-dev
Copy link
Contributor

Run Java PreCommit

@echauchot
Copy link
Contributor Author

@aromanenko-dev timeout in un unrelated portability test.

@echauchot
Copy link
Contributor Author

Run Java PreCommit

@echauchot
Copy link
Contributor Author

@aromanenko-dev all the tests pass, as you gave LGTM, I'll auto-merge. Thanks for the review !

@echauchot echauchot force-pushed the BEAM-8830-flattens-spark branch from f67bc41 to a9a68a8 Compare December 11, 2019 10:15
@echauchot
Copy link
Contributor Author

Run Spark StructuredStreaming ValidatesRunner

@echauchot
Copy link
Contributor Author

just reworded the last commit message

@echauchot
Copy link
Contributor Author

Run Java PreCommit

@echauchot echauchot merged commit 2080520 into apache:master Dec 11, 2019
@echauchot echauchot deleted the BEAM-8830-flattens-spark branch December 11, 2019 15:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants