Github user jeking3 commented on the issue:
https://github.com/apache/thrift/pull/1178
If the class has no testing at all then I would not require you to add
tests in order to get committed, however as Jens suggested it would improve the
quality of the project if tests were put in, so I always ask.
It looks like you are making modifications in your master branch and they
are getting sync'd into this pull request. In the future I would recommend
that you create a branch off master first, like "git checkout -b THRIFT-4072"
and then submit a pull request from that branch instead so it is isolated from
the changes in your master. There should only be one commit for your
changes... it looks like the way you have it set up, every time the apache
master is revised your pull request will rebuild here, which is a bit heavy.
If the previous build was clean I can merge this.
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
