https://bugs.freedesktop.org/show_bug.cgi?id=72324
--- Comment #14 from Karel Hruska <[email protected]> --- (In reply to comment #13) > (In reply to comment #12) > > The result of bibisection is bad: > > ... > > I was not even able to run these builds (ERROR 4 forking process). Should I > > create a separate bug report for this or is it possible to solve it together > > with rendering of graphical dependencies? > > AFAIK we don't currently test builds to make sure they will successfully run > prior to adding them to a bibisect repo. We hope that the number of > non-running builds remains small relative to the size of the repo. > > If you're unable to finish bibisecting a bug for technical reasons, please > feel free to make an note on the bug report, leave it for the developers or > other QA folks, and move on to the next bug in the list. If you'd like to > proceed further, you can try to build and run suspect versions based on what > bibisect has provided. Actually I am not sure if I expressed myself well - I did not mean a bugreport about non-running builds, but about bad rendering of dashed lines (from the attachment: https://bugs.freedesktop.org/attachment.cgi?id=100440). -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ Libreoffice-bugs mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
