On Wed, Jun 17, 2015 at 2:10 AM, Stephan Bergmann <sbergman@redhat.com> wrote:
On 06/17/2015 01:58 AM, Norbert Thiebaud wrote:
most likely candidate is prolly:
9b06d36571bbfa2d722f36610375e7cd24be81a7 reenable
JunitTest_dbaccess_complex part RowSet
...which should be easy to verify with "time make
JunitTest_dbaccess_complex" vs. "git revert
9b06d36571bbfa2d722f36610375e7cd24be81a7 && time make
JunitTest_dbaccess_complex", no?
Not when you have a build queue of 25 jobs, and are scrambling to
bring some ressource online to try to drain that queue before people
wake up and pile up again....
iow 100% of the Windows I have access are working hard to keep up... I
do not have spare to do this 'easy' thing....
I've narrowed it down to about 20 commits using build history data..
that, I could do without stopping builders....
Norbert
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.