You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are now some fontbakery tests (especially those in outline.py) that give different PASS messages (some of which are because there were so many warnings generated that the author decided they must be intentional and issued a PASS instead!). Example from outline.py:
if len(warnings) > FALSE_POSITIVE_CUTOFF:
# Let's not waste time.
yield PASS, ("So many Y-coordinates of points were close to"
" boundaries that this was probably by design.")
return
if warnings:
...
else:
yield PASS, "Y-coordinates of points fell on appropriate boundaries."
It would be good to provide a way to drop the loglevels to PASS. If we don't want PASS all the time, perhaps tie it to Pysilfont's loglevel, e.g., something like:
In psfrunfbchecks.py#L94:
we hardcode fontbakery's
loglevels
toSKIP
.There are now some fontbakery tests (especially those in
outline.py
) that give differentPASS
messages (some of which are because there were so many warnings generated that the author decided they must be intentional and issued aPASS
instead!). Example from outline.py:It would be good to provide a way to drop the
loglevels
toPASS
. If we don't wantPASS
all the time, perhaps tie it to Pysilfont'sloglevel
, e.g., something like:For that matter, though this is probably overkill, you could map:
I
==>INFO
V
==>PASS
The text was updated successfully, but these errors were encountered: