[
https://issues.apache.org/jira/browse/BEAM-4099?focusedWorklogId=91748&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-91748
]
ASF GitHub Bot logged work on BEAM-4099:
----------------------------------------
Author: ASF GitHub Bot
Created on: 17/Apr/18 13:28
Start Date: 17/Apr/18 13:28
Worklog Time Spent: 10m
Work Description: lgajowy opened a new pull request #5153: [BEAM-4099]
Rebuild project before running Performance tests on Jenkins
URL: https://github.com/apache/beam/pull/5153
Please see the detailed description in the [JIRA
issue](https://issues.apache.org/jira/browse/BEAM-4099).
------------------------
Follow this checklist to help us incorporate your contribution quickly and
easily:
- [x] Make sure there is a [JIRA
issue](https://issues.apache.org/jira/projects/BEAM/issues/) filed for the
change (usually before you start working on it). Trivial changes like typos do
not require a JIRA issue. Your pull request should address just this issue,
without pulling in other changes.
- [x] Format the pull request title like `[BEAM-XXX] Fixes bug in
ApproximateQuantiles`, where you replace `BEAM-XXX` with the appropriate JIRA
issue.
- [x] Write a pull request description that is detailed enough to
understand:
- [x] What the pull request does
- [x] Why it does it
- [x] How it does it
- [x] Why this approach
- [x] Each commit in the pull request should have a meaningful subject line
and body.
- [ ] Run `mvn clean verify` to make sure basic checks pass. A more
thorough check will be performed on your pull request automatically.
- [ ] If this contribution is large, please file an Apache [Individual
Contributor License Agreement](https://www.apache.org/licenses/icla.pdf).
----------------------------------------------------------------
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:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 91748)
Time Spent: 10m
Remaining Estimate: 0h
> Allways 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: 10m
> 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)
