2018-03-07 22:29 GMT+01:00 Kenneth Knowles <k...@google.com>: > > Based on https://builds.apache.org/view/A-D/view/Beam/ and our failure > spam level the performance tests are mostly not healthy anyhow. So is there > any high level blocker to switching them or is it just someone sitting down > with each one? > > I thought I could share my point of view here as I am working on the Performance Test part for a while now. I wouldn't say those are "mostly not healthy". The situation is as follows:
- totally not working: Python, Spark performance tests (don't know why, I'm not maintaining those tests. Should we disable them?) - flaky: the recently re-enabled JDBC Performance Test. It's seems to be flaky mostly due to: https://issues.apache.org/jira/browse/BEAM-3798 - working well, rarely failing: AvroIO, TextIO, Compressed Text, TFRecordIO Also, some test failures are caused due to pending PRs (we sometimes run concrete tests to check if PRs won't break them). This also causes failures sometimes. I can help with switching the Performance tests to Gradle as this part seems to be free to take. Łukasz
