I opened the new PR after I sent my e-mail below, so the script indeed was doing something weird.
On Wed, Aug 30, 2017 at 6:42 PM, Josh Rosen <joshro...@databricks.com> wrote: > I think that's because https://issues.apache.org/jira/browse/SPARK-21728 was > re-opened in JIRA and had a new PR associated with it, so the bot did the > temporary issue re-assignment in order to be able to transition the issue > status from "reopened" to "in progress". > > On Wed, Aug 30, 2017 at 1:18 PM Marcelo Vanzin <van...@cloudera.com> wrote: >> >> I'm still seeing some odd behavior. >> >> I just deleted my repo's branch for >> https://github.com/apache/spark/pull/19013 and the script seems to >> have done some update to the bug, since I got a bunch of e-mails. >> >> On Mon, Aug 28, 2017 at 2:34 PM, Josh Rosen <joshro...@databricks.com> >> wrote: >> > This should be fixed now. The problem was that debug code had been >> > pushed >> > while investigating the JIRA linkage failure but was not removed and >> > this >> > problem went unnoticed because linking was failing well before the debug >> > code was hit. Once the JIRA connectivity issues were resolved, the >> > problematic code was running and causing the linking operation to fail >> > mid-way through, triggering a finally block which undid the JIRA >> > assignment. >> > >> > I've rolled back the bad code and enabled additional monitoring in >> > StackDriver to raise an alert if we see new linking failures. >> > >> > On Mon, Aug 28, 2017 at 12:02 PM Marcelo Vanzin <van...@cloudera.com> >> > wrote: >> >> >> >> It seems a little wonky, though. Feels like it's updating JIRA every >> >> time you comment on a PR. Or maybe it's still working through the >> >> backlog... >> >> >> >> On Mon, Aug 28, 2017 at 9:57 AM, Reynold Xin <r...@databricks.com> >> >> wrote: >> >> > The process for doing that was down before, and might've come back up >> >> > and >> >> > are going through the huge backlog. >> >> > >> >> > >> >> > On Mon, Aug 28, 2017 at 6:56 PM, Sean Owen <so...@cloudera.com> >> >> > wrote: >> >> >> >> >> >> Like whatever reassigns JIRAs after a PR is closed? >> >> >> >> >> >> It seems to be going crazy, or maybe there are many running. Not >> >> >> sure >> >> >> who >> >> >> owns that, but can he/she take a look? >> >> >> >> >> > >> >> >> >> >> >> >> >> -- >> >> Marcelo >> >> >> >> --------------------------------------------------------------------- >> >> To unsubscribe e-mail: dev-unsubscr...@spark.apache.org >> >> >> > >> >> >> >> -- >> Marcelo -- Marcelo --------------------------------------------------------------------- To unsubscribe e-mail: dev-unsubscr...@spark.apache.org
