<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Segmentation fault in _cairo_traps_compositor_glyphs"
href="https://bugs.freedesktop.org/show_bug.cgi?id=103037#c23">Comment # 23</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Segmentation fault in _cairo_traps_compositor_glyphs"
href="https://bugs.freedesktop.org/show_bug.cgi?id=103037">bug 103037</a>
from <span class="vcard"><a class="email" href="mailto:ajohnson@redneon.com" title="Adrian Johnson <ajohnson@redneon.com>"> <span class="fn">Adrian Johnson</span></a>
</span></b>
<pre>(In reply to Mikhail Fludkov from <a href="show_bug.cgi?id=103037#c22">comment #22</a>)
<span class="quote">> I wanted to prepare libcairo package with the fix. We are still catching the
> crash in CI. Before doing that wanted to be sure that there are no
> undesirable side effects. So I run `make check` and the tests failed for me
> even without the patch.</span >
The image tests should mostly work but the other backends have a lot of
failures as it is very sensitive to the test environment (fonts, version of
freetype, gs, poppler, and rsvg). The way around it is to capture the output of
a run of the test suite before your changes, then use this output as the
reference images for testing your changes. This is documented in the README in
the test dir.
<span class="quote">>
> Do I need any special packages to run full test suite? When do you guys
> think the patch will be pushed to master branch?</span >
Unless any one has any more comments, I will run the test suite over it this
weekend then push it.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>