Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/9710#issuecomment-171470490
Will the code here need to update after a new version of that library is
released or will we only have to bump in Jenkins? If we won't have to do any
code changes, then I think we should go ahead and modify the other files to
also use this code. Since the few lines of test runner configuration might be
duplicated in a bunch of files, we could refactor them into a separate function
which we call in each file.
---
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.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
