Hello Stephan,
I understand your demand but I must also say that several times, I saw that:
- just rebasing might be sufficient to "fix" a Gerrit pb
- the pb wasn't related to the patch (eg: when a patch concerns something
specific to MacOs and Windows gerrit fails, or the contrary, typos in
comments like 99.9% of Andrea Gelmini's patches)
- failing gerrit because of technical error (eg: for retrieving some
components).
- aleatory failing QA tests (kind of "Heisenberg")
So it could be interesting too to make sure Gerrit machines are up-to-date
(rebooted if necessary), runned some "make clean" sometimes so they could be
more reliable.
Perhaps it's already the case but in these cases, how to make Gerrit
machines a bit more reliable?
But you're right, in general, Jenkins -1 shouldn't be overriden.
Julien
--
Sent from: http://document-foundation-mail-archive.969070.n3.nabble.com/Dev-f1639786.html
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.