[
https://issues.apache.org/jira/browse/BEAM-4099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Łukasz Gajowy updated BEAM-4099:
--------------------------------
Summary: Always rebuild beam before running Performance Tests on Jenkins
(was: Allways rebuild beam before running Performance Tests on Jenkins)
> Always rebuild beam before running Performance Tests on Jenkins
> ---------------------------------------------------------------
>
> Key: BEAM-4099
> URL: https://issues.apache.org/jira/browse/BEAM-4099
> Project: Beam
> Issue Type: Task
> Components: testing
> Reporter: Łukasz Gajowy
> Assignee: Łukasz Gajowy
> Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Currently performance tests running on Jenkins all have "beam_prebuilt" [1]
> Perfkit's flag set to true, which means that PerfKit does not rebuild the
> code before invoking the Performance Test. This makes things faster but error
> prone - we observed Performance Tests failures several times due to the fact
> that something was not built on time.
>
> We should rebuild Beam in every testing job to avoid errors (only "bare"
> build, without tests and checkstyle). This will make the tests last longer
> (about 7 minutes per each test, as my experiments have shown). Probably it
> will be faster on Gradle (didn't test it yet). There are 12 tests now with
> "beam_PerformanceTests_JDBC" as the longest lasting (total of 15 minutes).
> [1]
> https://beam.apache.org/documentation/io/testing/#implementing-integration-tests
> Link to mailing list discussion:
> [https://lists.apache.org/thread.html/503d284084103d605c8b56055ff82849784914b99549630977df5214@%3Cdev.beam.apache.org%3E]
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
