Are you sure? That seems like a very odd thing… not saying you are wrong, but this seems like a
very odd thing to have as a requirement for a unit test.
Chris
On 14 Feb 2016, at 6:47 PM, Mark Hung <marklh9@gmail.com> wrote:
Hi Chris,
It is possible that for some tests need --enable-dbgutil or make debug=true to trigger the assert.
Best Regards.
2016-02-14 15:14 GMT+08:00 Chris Sherlock <chris.sherlock79@gmail.com
<mailto:chris.sherlock79@gmail.com>>:
Hi all,
https://gerrit.libreoffice.org/#/c/20993/ <https://gerrit.libreoffice.org/#/c/20993/> on Gerrit,
and fixes bug 96749 (deal with missing custom headers/footers in docx).
I’ve cherry picked this and built this on my Ubuntu Linux system from master, and I’m getting no
unit test failures.
Jenkins, however, is failing on both Linux and Mac OS X, but interestingly not Windows. On Linux
the failure is:
http://ci.libreoffice.org/job/lo_gerrit_master/11877/Gerrit=Gerrit,Platform=Linux/console
<http://ci.libreoffice.org/job/lo_gerrit_master/11877/Gerrit=Gerrit,Platform=Linux/console>
Anyone have any ideas why this failure is occuring when it isn’t occuring on my local Linux
system?
(Incidentally, the fix is good and works really well).
Chris
_______________________________________________
LibreOffice mailing list
LibreOffice@lists.freedesktop.org <mailto:LibreOffice@lists.freedesktop.org>
https://lists.freedesktop.org/mailman/listinfo/libreoffice
<https://lists.freedesktop.org/mailman/listinfo/libreoffice>
--
Mark Hung
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.