GitHub user kennknowles opened a pull request: https://github.com/apache/beam/pull/2207
[BEAM-1663] Use stable naming strategy for ByteBuddy invokers This helps to coalesce related failures across multiple JVM instances, over time, across machines, etc. Be sure to do all of the following to help us incorporate your contribution quickly and easily: - [ ] Make sure the PR title is formatted like: `[BEAM-<Jira issue #>] Description of pull request` - [ ] Make sure tests pass via `mvn clean verify`. (Even better, enable Travis-CI on your fork and ensure the whole test matrix passes). - [ ] Replace `<Jira issue #>` in the title with the actual Jira issue number, if there is one. - [ ] If this contribution is large, please file an Apache [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.txt). --- You can merge this pull request into a Git repository by running: $ git pull https://github.com/kennknowles/beam bytebuddy-names Alternatively you can review and apply these changes as the patch at: https://github.com/apache/beam/pull/2207.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #2207 ---- commit 01d32c026dd5dafff17f0c95a63278f95b159d8d Author: Kenneth Knowles <k...@google.com> Date: 2017-03-09T01:02:05Z Use stable naming strategy for ByteBuddy invokers This helps to coalesce related failures across multiple JVM instances, over time, across machines, etc. ---- --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---