Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

harfbuzz-1.3.2 (and 1.3.1) fail shaping/vertical.tests on Gentoo #337

Closed
PPed72 opened this issue Oct 4, 2016 · 11 comments
Closed

harfbuzz-1.3.2 (and 1.3.1) fail shaping/vertical.tests on Gentoo #337

PPed72 opened this issue Oct 4, 2016 · 11 comments
Labels
invalid Not a HarfBuzz bug

Comments

@PPed72
Copy link

PPed72 commented Oct 4, 2016

See also: https://bugs.gentoo.org/show_bug.cgi?id=596124

# cat /var/tmp/portage/media-libs/harfbuzz-1.3.2/work/harfbuzz-1.3.2-abi_x86_64.amd64/test/shaping/test-suite.log
=================================================
   HarfBuzz 1.3.2: test/shaping/test-suite.log
=================================================

# TOTAL: 21
# PASS:  20
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

.. contents:: :depth: 2

FAIL: tests/vertical
====================

Running tests in /var/tmp/portage/media-libs/harfbuzz-1.3.2/work/harfbuzz-1.3.2/test/shaping/tests/vertical.tests
Testing fonts/sha1sum/191826b9643e3f124d865d617ae609db6a2ce203.ttf:U+300C
Actual:   [uni300C.vert=0@-448,-578+0,-1024]
Expected: [uni300C.vert=0@-512,-578+0,-1024]
1 tests failed.

harfbuzz-1.3.2:20161004-094340.log.gz

@khaledhosny
Copy link
Collaborator

Can you reproduce the failure with older versions of HarfBuzz, or is it specific to 1.3.2 and 1.3.1? I can’t reproduce this locally.

@PPed72
Copy link
Author

PPed72 commented Oct 4, 2016

In data martedì 4 ottobre 2016 03:33:30 CEST, Khaled Hosny ha scritto:

Can you reproduce the failure with older versions of HarfBuzz, or is it
specific to 1.3.2 and 1.3.1? I can’t reproduce this locally.

1.2.7 worked fine for me.

Paolo Pedroni
Email: paolo.pedroniiol.it

@khaledhosny
Copy link
Collaborator

There are not that many commits between 1.2.7 and 1.3.1, so it would be helpful if you can git bisect them to find the commit introducing this. At a first glance I don’t see anything that could be related.

@PPed72
Copy link
Author

PPed72 commented Oct 4, 2016

In data martedì 4 ottobre 2016 04:36:47 CEST, Khaled Hosny ha scritto:

There are not that many commits between 1.2.7 and 1.3.1, so it would be
helpful if you can git bisect them to find the commit introducing this. At
a first glance I don’t see anything that could be related.

It must be some dependency, because now 1.2.7 fails as well...

I'll try to see what might have caused it.

Paolo Pedroni
Email: paolo.pedroniiol.it

@PPed72
Copy link
Author

PPed72 commented Oct 4, 2016

Which version of glib are you using? I have 2.48.2 on my system which is failing tests, while I had 2.46.2 last time tests succeeded. Sadly I can't downgrade glib to test if it's the real culprit. Everything else that's changed between then and now does not make a difference...

@khaledhosny
Copy link
Collaborator

I have 2.48.2 here as well. Though I think glib is unlikely to be involved in this, FreeType is a more likely candidate.

@behdad
Copy link
Member

behdad commented Oct 4, 2016

Definitely FreeType change.

@PPed72
Copy link
Author

PPed72 commented Oct 4, 2016

The only thing that changed in freetype is that I enabled infinality. Tomorrow I will check for that.

Paolo Pedroni
Email: paolo.pedroniiol.it
Il 04 ott 2016 6:44 PM, Behdad Esfahbod notifications@github.com ha scritto:Definitely FreeType change.

—You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or mute the thread.

@behdad
Copy link
Member

behdad commented Oct 4, 2016

The only thing that changed in freetype is that I enabled infinality

That always explains everything!!

@khaledhosny
Copy link
Collaborator

@PPed72 did you try without Infinality?

@PPed72
Copy link
Author

PPed72 commented Oct 20, 2016

Yes, I did, and it worked. It seems I forgot to follow up on this thread, sorry.

@khaledhosny khaledhosny added the invalid Not a HarfBuzz bug label Oct 20, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
invalid Not a HarfBuzz bug
Projects
None yet
Development

No branches or pull requests

3 participants