-
Notifications
You must be signed in to change notification settings - Fork 99
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
Investigate why some git_repos fail to run fbakery on container-engine #1240
Labels
Comments
These are the families (from our initial selection of 34 font repos) that are failing to run fontbakery on the worker container:
|
OK. I just noticed a pattern! These are the families that place the font files right in the root dir. The issue must be related to the way I extract the font-files directory path. I'll surely find a bug in there and fix it :-) |
yes, indeed! |
:D
|
felipesanches
added a commit
to felipesanches/fontbakery
that referenced
this issue
Mar 28, 2017
* updating Dockerfile to accomodate recent refactoring that has split code into multiple external modules * the most common reason for failing to run fontbakery on the worker container was that the git log command was not including the HEAD commit of the git tree. * fixed some more bad unicode string handling * updated the deploy script * added a workaround for TargetFont not being JSON-serializable (when outputing check-results in JSON format) (fix issue fonttools#1240)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I've setup the dispatcher to queue 34 git repos for processing by the worker container.
When the workers run, some of these font projects fail to be properly checked by fontbakery. From 34 projects, only 21 show up in the dashboard UI.
The text was updated successfully, but these errors were encountered: