[21:32] veebers: is there something wrong with the merge bot? [21:32] thumper: not that I'm aware of, whats the issue/ [21:32] thumper: (which merge job?) [21:33] I was just looking at one of jam's branches [21:33] saw the merge request but no bot response [21:33] https://github.com/juju/juju/pull/8557 [21:33] thumper: it's possible it's the issue where the hook gets dropped or ignored by jenkins. [21:33] do the checks on a PR get cleared on new pushes? [21:34] thumper: checks get re-run on pushes. (you can see ticks/crosses beside the commit sha in the list) [21:35] I know that the merge jobs just show up as checks now... [21:35] perhaps it was just that [21:35] never mind me [21:35] thumper: If the merge bot had run it would have been merged, unless there was an issue then it would show as a failure [21:36] but we don't add a comment on failure, do we? [21:36] thumper: if you click "show all checks" you'll see that only the check-merge job has run [21:36] thumper: it would show up in the checks list [21:37] ah, found it [21:38] thumper: argh, so the merge job did run (before your current one) and went unstable, no idea why it didn't update the PR. :-\ Having a quick look now [21:38] ok, thanks [21:51] thumper: I'm a little confused :-\ jams merge command worked, it ran and failed and marked that commit broken (red cross) but it wasn't mentioned in the checks section. Jam then pushed up some . .. ah [21:51] thumper: It seems that pushing up a commit and getting a run on it clears any previous runs (incl. failures) so the updated push removed the check comment for the failed merge (it was still marked as error by the red cross though) [21:52] * veebers is no longer confused [21:52] * thumper nods [21:57] morning wallyworld [21:57] hey [21:57] veebers: do you use spacemacs with vim editing or emacs? [22:08] thumper: emacs [22:08] wallyworld: hey o/ [22:08] hiya [22:09] o/