[07:51:51] <wikibugs>	 10Quibble: Provide early feedback when a patch has job failures - https://phabricator.wikimedia.org/T323750 (10kostajh)
[07:52:30] <wikibugs>	 10Quibble: Provide early feedback when a patch has job failures - https://phabricator.wikimedia.org/T323750 (10kostajh) @hashar what do you think? I'd be happy to hack on Quibble/web app for this, if you think it's useful.
[08:00:56] <wikibugs>	 10Quibble, 10Continuous-Integration-Infrastructure, 10Developer Productivity: Provide early feedback when a patch has job failures - https://phabricator.wikimedia.org/T323750 (10kostajh)
[08:29:14] <wikibugs>	 10Quibble, 10Continuous-Integration-Infrastructure, 10Developer Productivity: Provide early feedback when a patch has job failures - https://phabricator.wikimedia.org/T323750 (10hashar) Ideally Zuul would report immediately when it knows that a change is not going to pass. As you found out that is T248531 wh...
[08:29:20] <hashar>	 kostajh: https://phabricator.wikimedia.org/T214068#8410529 ;)
[08:29:23] <hashar>	 that is the tldr
[08:29:43] <hashar>	 the idea is to have Gerrit to expose the status in Zuul an hopefully folks willl notice a build error immediately
[08:29:54] <hashar>	 I wrote a summary on your task
[08:30:33] <hashar>	 I wanna write the doc today or tomorrow as to how one can potentially test the code I wrote by side loading a plugin inside the Gerrit interface
[08:44:24] <kostajh>	 cool
[08:44:42] <kostajh>	 but would that also trigger email/irc notices? I think that is important
[08:45:26] <kostajh>	 outsourcing this work to a web app that leaves a comment would also allow for surfacing the exact error messages, without the developer needing to click the url, and scroll to the bottom of a page
[09:28:13] <hashar>	 kostajh: that can possibly be done from the Gerrit web UI by retrieving the jenkins build artifact / console and have displayed in the Gerrit UI
[11:58:29] <kostajh>	 ack