Skip to content

Error (failed with exit code 1) in GitHub Action check #3136

Discussion options

You must be logged in to vote

When your font project has some problem detected by FontBakery, the tool returns a non-zero error code which is often used by other tools such as the GitHub Actions infrastructure to detect that something went wrong. That's why you get a "broken build" in this case. This is the expected behaviour, it is not a bug.

You should look at the GitHub Actions build log to get the full details on what are the problems that FontBakery detected in the latest commit of your font project repo. You will see some FAIL messages (highlighted in red), and maybe also some WARN messages (in yellow). You must address the FAIL ones and should at least consider what the WARN ones tell you.

Here's one of those FAIL

Replies: 2 comments 5 replies

Comment options

You must be logged in to vote
5 replies
@philippnurullin
Comment options

@philippnurullin
Comment options

@philippnurullin
Comment options

@chrissimpkins
Comment options

@philippnurullin
Comment options

Answer selected by felipesanches
Comment options

You must be logged in to vote
0 replies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
3 participants
Converted from issue

This discussion was converted from issue #3136 on December 27, 2020 13:40.