Hi Stephan, On Wed, Nov 29, 2017 at 12:16:24PM +0100, Stephan Bergmann <sberg...@redhat.com> wrote: > Is there any good reason why a failed Gerrit/Jenkins build does not set the > corresponding Gerrit change's Verified flag to -1 (similar to how a > successful such build sets the flag to +1)? > > Especially with the poor Jenkins turnaround times, it is hard to tell on a > page like <https://gerrit.libreoffice.org/#/dashboard/self> whether a change > is not yet ready for submission because Jenkins has not yet built it or > because the Jenkins build failed. The "V" ("Verified") column is empty in > both cases. (And I assume it would contain something like a red cross if > the Verified flag is -1.)
I think this was a decision from Norbert, probably because he was worried about false negatives. A workaround is to watch your inbox (which gets a mail, whatever is the outcome), rather than the above URL. (I would have no problem if Jenkins would put a Verified-1, though.) Regards, Miklos
signature.asc
Description: Digital signature
_______________________________________________ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
