Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/2581#issuecomment-57220286
this is happening because we have two GHPRB bots: AmplabJenkins (which we
control), and SparkQA (which is apache/databricks).
GHPRB will only allow one "master" bot, which is AmplabJenkins, as is used
for all projects that are not spark related.
to work around this, the dbricks folks have set up SparkQA, which is a
special/custom bot that uses a shell script in the build and password
injection to post build messages.
i also looked around and there doesn't seem to be an easy way to have
amplab jenkins ignore spark repos. this means that we're probably going to
be seeing some duplicate messages like this for the near future (short of
us running a custom PRB bot, while being feasible, is really low on the
amplab list of priorities).
i know josh was looking at running a custom PRB plugin, so maybe he can
chime in. :)
On Mon, Sep 29, 2014 at 12:35 PM, Nicholas Chammas <[email protected]
> wrote:
> Test FAILed.
> Refer to this link for build results (access rights to CI server needed):
> https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/20984/
>
> @JoshRosen <https://github.com/JoshRosen> @shaneknapp
> <https://github.com/shaneknapp> Any updates on why Jenkins is posting
> these duplicate messages to GitHub? They don't appear to be triggered by
> any code in this repo.
>
> â
> Reply to this email directly or view it on GitHub
> <https://github.com/apache/spark/pull/2581#issuecomment-57215864>.
>
---
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.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
